On Tue, Nov 26, 2013 at 5:17 PM, David Goulet wrote:
> Hi everyone,
>
> The torsocks 2.0-rc3 code is getting quite stable in my opinion. There
> are still some issues but nothing feature critical.
>
> https://github.com/dgoulet/torsocks
>
> I would really love to have help with code review
On Sat, Nov 30, 2013 at 12:02 PM, Nathan Freitas wrote:
> Now that Orchid is released at a v1 stage, I have been thinking about having
> Orbot use it by default, and then offering ARM and x86 binaries as add-on
> enhancements. This would make the core Tor on Android experience more
> lightweight f
Now that Orchid is released at a v1 stage, I have been thinking about having
Orbot use it by default, and then offering ARM and x86 binaries as add-on
enhancements. This would make the core Tor on Android experience more
lightweight for client only use. If people want to run relays, need a highe
On 30 Nov (14:22:19), Philipp Winter wrote:
> On Fri, Nov 29, 2013 at 11:37:27AM -0500, David Goulet wrote:
> > On 29 Nov (15:07:41), Philipp Winter wrote:
> >> I also have a minor feature request. It would be great if
> >> torsocks could display the source IP address and port of
> >> connections.
On Fri, Nov 29, 2013 at 11:37:27AM -0500, David Goulet wrote:
> On 29 Nov (15:07:41), Philipp Winter wrote:
>> I also have a minor feature request. It would be great if
>> torsocks could display the source IP address and port of
>> connections. I'm currently working on a Tor controller
>> compone
Relative to what's in the draft it's an improvement with no obvious downside.
If you were going to do this it would probably be best to use a full
commitment order instead of only selecting the final committer. That
is, instead of having an n'th committer and n-1 chaotically ordered
committers you
