On Tue, Jan 12, 2016 at 11:49:19PM +, John wrote:
> Hi David,
>
> Thank you, these pointers were very helpful. Do you know if there is
> some kind of resource that lists known censorship events? I'd like to
> see how good the approach from the paper does at identifying them.
For Tor-specific
> On 13 Jan 2016, at 00:53, Mike Perry wrote:
>
> This proposal aims to allow us to load balance properly between Guard,
> Middle, and Exit nodes with the addition of padding traffic to the
> network.
> ...
> 1. Overview
>
> For padding overhead due to Proposals 251 and 254, and changes to hidd
> On 13 Jan 2016, at 01:46, George Kadianakis wrote:
>
> Hello there,
>
> we are happy to tell you that we finished coding proposal 250 and our first
> attempt at implementation is ready for review.
>
> You can find the final specification here:
>
> https://gitweb.torproject.org/user/dgou
Hi David,
Thank you, these pointers were very helpful. Do you know if there is
some kind of resource that lists known censorship events? I'd like to
see how good the approach from the paper does at identifying them.
--john
David Fifield:
> On Tue, Jan 12, 2016 at 07:21:39AM +, John wrote:
>
On Tue, Jan 12, 2016 at 09:40:35AM +0100, Karsten Loesing wrote:
> Philipp, would you be able to write the Zoossh counterpart for the
> descriptor types supported by it? I'm even more curious now how those
> numbers compare to metrics-lib and Stem.
I'd love to, but I cannot promise when I'll be d
Hi,
>
> Nathan Freitas:
> I've got big plans for Orbot in 2016...
> any thoughts on the roadmap below:
>
> More Orbot VPN features including
> better UI for enabling/disabling
> Torouting,
>
I love the animation when swapping identities but it is challenging to discover.
>
> blocking specif
On 12/01/16 16:16, Nathan Freitas wrote:
> The broader idea is to determine which Tor torrc settings are relevant
> to the mobile environment, and that could use a more intuitive user
> interface than the empty text input we currently offer in our Settings
> panel. This may also mean implement a sl
Thanks! Yup, those results look reasonable. I was expecting a smaller
delta with server/extrainfo descriptors and larger one with
microdescriptors due to the lazy loading but oh well. What stem commit
and python version was this with?
Any thoughts on when you'll have time to clean up the metrics-l
On Tue, Jan 12, 2016, at 10:48 AM, Georg Koppen wrote:
> Nathan Freitas:
> > - Overall improved configuration / settings UI to make tuning Orbot a
> > better, simpler experience... this is an expansion of the new exit
> > country selector in Orbot v15.1, but also includes managing things like
> > n
Nathan Freitas:
> - Overall improved configuration / settings UI to make tuning Orbot a
> better, simpler experience... this is an expansion of the new exit
> country selector in Orbot v15.1, but also includes managing things like
> network usage and so on.
Could you explain that point a bit more,
I've got big plans for Orbot in 2016... any thoughts on the roadmap
below, particularly how it aligns with Tor core roadmap, would be
appreciated.
- Original message -
From: Nathan of Guardian
To: guardian-...@lists.mayfirst.org
Subject: Orbot roadmap feedback
Date: Mon, 11 Jan 2016 22:58
On Mon, Jan 11, 2016 at 9:16 AM, Zhenfei Zhang
wrote:
> Hi list,
>
> Thanks for all your valuable comments.
> We have updated the feature request following your comments.
> Please see the attachment for the updated feature request, and see
> https://github.com/zhenfeizhang/ntru-tor/commit/0354fe1d
On 1/12/16, Tim Wilson-Brown - teor wrote:
> ...
> The current tor implementation simply calls connect() if OutBoundBindAddress
> is not set for the destination address family.
> This means that the connection will be made from a source address based on
> the routing table entry for the destinatio
Hello there,
we are happy to tell you that we finished coding proposal 250 and our first
attempt at implementation is ready for review.
You can find the final specification here:
https://gitweb.torproject.org/user/dgoulet/torspec.git/log/?h=prop250_final_v1
and the corresponding code here:
This proposal aims to allow us to load balance properly between Guard,
Middle, and Exit nodes with the addition of padding traffic to the
network.
Canonical proposal current lives in my load_balancing-squashed branch:
https://gitweb.torproject.org/user/mikeperry/torspec.git/tree/proposals/xxx-load
> On 12 Jan 2016, at 21:01, Fabio Pietrosanti (naif) - lists
> wrote:
>
>
>
> On 1/12/16 4:43 AM, David Fifield wrote:
>> I wanted to know how many exits exit from an address that is different
>> from their OR address. The answer is about 10.7%, 109/1018 exits. The
>> interesting part is that
On 1/12/16 4:43 AM, David Fifield wrote:
> I wanted to know how many exits exit from an address that is different
> from their OR address. The answer is about 10.7%, 109/1018 exits. The
> interesting part is that of those 109 mismatches, 87 have an exit
> address that differs from the OR address
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/01/16 05:38, Damian Johnson wrote:
> Hi Karsten, implemented Stem counterparts of these (see attached).
> On one hand the code is delightfully simple, but on the other
> measurements I got were quite a bit slower. Curious to see what
> you get w
18 matches
Mail list logo
