Now that Tor (as of 0.2.3.x) supports optimistic data, we should try to get torsocks to support it.
This won't be totally trivial, since we'll need to tell the application "yes, it connected" early, and then give an error if the connection actually happens. (Perhaps we can get away with doing an early shutdown() on the connection so that reads and writes fail, but the fd lingers. If not, we'll have to intercept read, write, pread, pwrite, writev, select, etc, so that we can give an error if needed.)
There was some discussion of this in the comments of #1849 (moved).
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items 0
Link issues together to show that they're related.
Learn more.
It's not complete yet, but I appreciate any reviews. It's been tested on OSX 10.6, Debian and Gentoo using curl, wget, and git. Once it's complete I'll rebase in a different branch.
This patchset adds support for shimming recvmsg, read, write, send, recv, recvfrom, writev, readv, sendmmsg, recvmmsg, ppoll, pselect, epoll_wait, epoll_pwait
This list will likely grow to support many of the other relevant non-Linux and non-POSIX syscalls that are out there. Please point me in the right direction :)
The reason is that I wanted to make sure the basic functionalities are reviewed, tested and working well with a fairly good test coverage (still in the making). Also, if this version is accepted by the community as a replacement to the current torsocks, I really want to add optimistic data as a new feature.
I already have a dev. branch (not ready for merge though) and started to play a bit with it. After a 2.0-stable release, this is certainly one of my main focus.