On Wed, Nov 4, 2015 at 1:18 PM, Sukhbir Singh wrote:
> Hi Greg,
>
> > Hi all,
> >
> > First of all, great work on Tor Messenger - it's awesome to see Tor
> pushing
> > to be more accessible to non-technical folks.
> >
> > I decided to take some notes when installing + using for
> On 3 Nov 2015, at 13:01, Nick Mathewson wrote:
>
> Secondary meeting time and patch workshop:
> Monday at 0100 UTC (8:00pm EST, 5:00pm PST)
Hi Nick,
I'm not sure which time zones "Monday" refers to.
Is the Secondary meeting time and patch workshop:
Tuesday at 0100
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
asn,
Is it possible to add a field called 'NOTARY' in the COMMIT and REVEAL
values where we include the SR pubkey + certificates and everything we
need so that we can validate each COMMIT / REVEAL value and tie it to
the identity of a directory
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
Epic work. I agree that the code enforcing commit majority was not
making a difference in the partition attack. I also agree that the
partition attack is (almost) useless, expensive and very noisy. An
attacker can get the same result if,
Thanks to all for the feedback.
That Torflow works from links slower than those of the fastest relays seems to
indicate it's measuring relative path resistance as much or more than absolute
bandwidth. I often see it produce sensible results and hope that some tuning
and fixing might produce
On Wed, Nov 4, 2015 at 4:06 AM, Karsten Loesing wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello developers,
>
> in the past few days I have been working on a grammar to parse Tor
> bridge network statuses and hopefully other Tor descriptors in the
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello devs,
we'll have another 1-1-1 task exchange meeting on
Thursday, November 5, 2015, 15:00 UTC in #tor-dev
https://www.timeanddate.com/worldclock/fixedtime.html?iso=20151105T15
Quick reminder: The idea of the 1-1-1 task exchange meeting is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello developers,
in the past few days I have been working on a grammar to parse Tor
bridge network statuses and hopefully other Tor descriptors in the
future. It's working, for some definition of working, but some issues
remain and I need some
On Tue, Nov 03, 2015 at 09:32:26PM -0800, Jesse V wrote:
> Yep, I've run Mike Perry's code before. It's all in torflow. I was also on a
> 1 gbits link, but as I recall it wasn't that saturated so you might be able
> to get away with a 500 mbits.
I've been running it on a 100mbit link, and it