On Nov 3, 2011, at 9:08 PM, Watson Ladd wrote:
> Dear all,
>
> Recently Zooko forwarded an email asking why we have to migrate. I am
> outlining the reasons in this email why I believe Tor needs to
> use stronger cryptography very soon.
>
> Tor currently uses RSA-1024 bit keys for OR public ide
Dear all,
Recently Zooko forwarded an email asking why we have to migrate. I am
outlining the reasons in this email why I believe Tor needs to
use stronger cryptography very soon.
Tor currently uses RSA-1024 bit keys for OR public identities and
1024-bit Diffie Hellman for the negotiation of keys
Dear all,
I read arma's blog entry calling for someone to see if limiting
zig-zag attacks would harm anonymity. Well, I don't have an answer,
but I did notice that we could increase the number of bridge
authorities by having each bridge authority take a distinct subset of
bridges to hand out, and t
On Thu, Nov 3, 2011 at 6:30 PM, Watson Ladd wrote:
> Dear all,
> Here is a patch that removes crypto cruft from torspec.txt. It does
> make torspec unusable because we haven't written crypto.txt yet.
> In the process I noticed a few things I cleaned up, and also noticed
> that RELAY_EXTEND cells h
Zooko forwarded a hash question over to the SHA-3 competition mailing list, and
mentioned the discussion that has been going on here. He's going to forward
over comments that I made and John Kelsey made. Nonetheless, I'd like to offer
some comments on what I've read in a larger context.
I don't
Dear all,
Here is a patch that removes crypto cruft from torspec.txt. It does
make torspec unusable because we haven't written crypto.txt yet.
In the process I noticed a few things I cleaned up, and also noticed
that RELAY_EXTEND cells have to be understood by both ORs, which
could be an impediment
Dear All,
What precisely is the timestamp? Right now it says "number of seconds
since the Unix epoch" which leaves open TAI, UTC, or UT1. We probably
are using UTC so I should say that, but I just want to make sure.
Sincerely,
Watson Ladd
___
tor-dev mail
