Tahoe-LAFS is incompatible with non-ancient Torsocks

[dawuud]

It is my understanding that Tahoe-LAFS only works with older versions of Torsocks; 1.x. However it is utterly incompatible with Torsocks versions 2.x and 3.x... This seems like it may be due to several reasons... namely Torsocks not handling non-blocking sockets properly.

Would Leif Ryge like to add more details to this ticket?

[leif]

I think torsocks 2.0 sort of works now; tahoe is just non-responsive for a minute or so after it starts. (It would be nice to know why that is and fix it, though!)

I just now noticed that the other issue (with torsocks blocking listenUDP) was actually fixed on master in December (see #2296) and I also recall seeing warner write somewhere recently that that codepath is not even used anymore if tub.location is set. (dawuud: when we were testing in valencia we were using the release in debian and also the truckee branch which hasn't had master merged since before then.)

[daira]

Yes, as a side-effect of the fix to #754 (which will be released in Tahoe-LAFS 1.10.1), setting tub.location without including "AUTO" will skip the local IP auto-detection code entirely.

[warner]

Milestone renamed