David Goulet: > Now the issue was detected with firefox which uses a custom malloc hook > meaning that it handles its own memory allocation. This hook uses mmap() > that firefox redefines to be a direct syscall(__NR_mmap, ...) and > remember that this symbol is hijacked by torsocks. > [â] > It's a bit of a catch 22 because torsocks is basically looking for the > libc syscall symbol but then it gets call inside that lookup code > path... Wouldn't one way out be to also hook malloc to use a static buffer until dlsym() is done? The code snippet in the following answer is doing just that: <http://stackoverflow.com/a/10008252> -- Lunar <lunar@xxxxxxxxxxxxxx>
Attachment:
signature.asc
Description: Digital signature
_______________________________________________ tor-dev mailing list tor-dev@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev