On 7/28/12, Zack Weinberg wrote:
> [I'm moving this from a giant cc: list to tor-dev, I hope that's okay.
> I *think* everyone involved is already on that list.]
>
> [I apologize for not picking up this ball for so long, I have been ill
> and mostly without the brain.]
>
> On Sun, Jul 22, 2012 at
[I'm moving this from a giant cc: list to tor-dev, I hope that's okay.
I *think* everyone involved is already on that list.]
[I apologize for not picking up this ball for so long, I have been ill
and mostly without the brain.]
On Sun, Jul 22, 2012 at 2:26 AM, Robert Ransom wrote:
>
> Specifical
On Wed, Jul 25, 2012 at 11:56 PM, Robert Ransom wrote:
> On 7/26/12, David Fifield wrote:
>
>> We can use appid-like signatures to make steganographic channels, if we
>> assume that the signatures are a realistic reflection of actual use of
>> the protocols. But: this relies critically on the acc
On 7/28/12 11:44 AM, Sathyanarayanan Gunasekaran wrote:
> If you want some sample summary, bandwidth, or details documents to
> see see how they look like, I can send you the ones I got from Karsten
> during the Tor dev meeting.
Oh, I wasn't aware that Sathya is working on the backend and Megan an
Hi,
>> We were
>> wondering what some of the entries might look like so we would be able to
>> see what information was being parsed to fill in some of the fields such as
>> the bandwidth handler's "write_history" and "read_history". We noticed that
>> the router descriptor format includes "write_
Hi Megan, hi Erik,
cc'ing Sathya and tor-dev, hoping you don't mind.
On 7/27/12 5:21 PM, Megan Chang wrote:
> We are currently almost done with the first draft of pyonionoo.
Awesome! :)
> We were
> wondering what some of the entries might look like so we would be able to
> see what information
