On Thu, Jan 21, 2016, at 10:11 AM, Michael Rogers wrote: > I've just fixed a bug in Briar that was caused by switching to the > version of jsocks published in JCenter. As far as I can tell, that jar > is based on an unmaintained and broken fork of jsocks by ConnectBot. > > While investigating the bug I found at least four other versions of > jsocks: > > * The original, https://sourceforge.net/p/jsocks > * Google's fork, https://code.google.com/p/jsocks-mirror > * code4craft's fork, https://github.com/code4craft/jsocks > * ravn's fork, https://github.com/ravn/jsocks > > Various people (now including me) have exported Google's fork to GitHub, > and it looks like the Guardian Project has forked ravn's fork. > > I haven't been able to work out how the various forks are related to > each other, but ConnectBot's fork seems to be the only one that's > broken. Unfortunately it's also the only one with a published jar. So I > wanted to ask whether you guys might be interested in working together > to publish a jar based on one of the non-broken forks.
Yes, that would be excellent. The main changes I made were related to working with the Orbot VPN feature. This could be done via a generic interface for knowing when Sockets are created. https://github.com/guardianproject/jsocks/commits/master -- Nathan of Guardian [email protected] _______________________________________________ List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev To unsubscribe, email: [email protected]
