Thanks for everybody who participated last week. The summary of the
meeting can be found here:
https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/meetings/20130913BiWeeklyPT
We decided that we are going to have these meetings biweekly till we see
if we need more or less frequen
On 9/19/13, Nick Mathewson wrote:
> On Thu, Sep 19, 2013 at 4:53 AM, grarpamp wrote:
>> I suggest a solution to transporting IPv6 within Tor be
>> maintained/deployed concurrently with any change in
>> current onion addressing and or transport mechanics.
>
> I have nothing against onioncat, but l
On Thu, Sep 19, 2013 at 4:53 AM, grarpamp wrote:
> On 9/13/13, George Kadianakis wrote:
>> This proposal is in serious need for comments.
>
>> 1.2. From the PoV of the HS client:
>>
>> Tor clients can distinguish new-style HS addresses from old ones by
>> their length. Legacy addresses are 16
On Fri, Sep 13, 2013 at 6:54 AM, Leif Ryge wrote:
> On Wed, Sep 11, 2013 at 11:20:59AM -0400, Nick Mathewson wrote:
[...]
>> To avoid confusion, I would phrase that as not as "reveals their
>> location to the adversary" but as "shows the adversary that
>> connections are all coming from the same
On Fri, Sep 13, 2013 at 10:39 AM, George Kadianakis
wrote:
> Here is another HS proposal draft.
>
[...]
> 1.1. From the PoV of Hidden Services:
>
> === XXX DISCUSSION XXX ===
>
> I see (at least) three migration strategies here. I'm not sure which
> one is better so I'll write all of them a
On Wed, Sep 18, 2013 at 11:57 PM, Roger Dingledine wrote:
> Hi Nick, Ian,
>
> I've been pointing people to "Section 6 of
> http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.228.6223"; when
> they ask what NTor is. But then I realized that that's not the best
> (single) place to send cryptogr
Hi Damian,
Roger and I discussed the consensus-health web page that the Java
version of DocTor produces [0] but your Python version does not. Roger
says he uses that page to debug the Tor network. In particular, he says
he scans the huge relay flags table to spot differences between relay
flags
Hi Aaron, Sathya,
I have another use for your fine path simulator. :)
See https://trac.torproject.org/projects/tor/ticket/9777
The first question is: for a recent consensus, what's the chance that
your middle hop and your exit hop will both be running 0.2.4.7-alpha
or earlier?
The extra credit
On 9/13/13, George Kadianakis wrote:
> This proposal is in serious need for comments.
> 1.2. From the PoV of the HS client:
>
> Tor clients can distinguish new-style HS addresses from old ones by
> their length. Legacy addresses are 16 base32 characters, while new
> ones are 56 (XXX) base32
