Re: [tor-dev] Quantum-safe Hybrid handshake for Tor

Wasn't there a transition period in migrating from RSA to ECC? Maybe I'm just confused. Or you are confused. But I think it is best plan for a five or ten year transition period. ___ tor-dev mailing list tor-dev@lists.torproject.org

Re: [tor-dev] Quantum-safe Hybrid handshake for Tor

> > We had a GSOC project to produce "consensus diffs", so that clients could > download the differences between each consensus each hour, rather than > downloading a full consensus (~1.5MB). > > It showed some great results, but still needs a little work before we merge >

[tor-dev] Quantum-safe Hybrid handshake for Tor

Hi, s7r: quantum computers don't exist... Yet: http://www.amarchenkova.com/about/ Wordlife, Spencer ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

Re: [tor-dev] Comparing Stem, metrics-lib, and zoossh

Nice! Few questions... * Where are your metrics-lib scripts used for the benchmarks? Should be easy for me to write stem counterparts once I know what we're running. I'll later be including our demo scripts with the benchmarks later so if possible comments would be nice so they're good examples

Re: [tor-dev] Quantum-safe Hybrid handshake for Tor

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 1/3/2016 11:24 PM, Ryan Carboni wrote: > > Given the slow time it takes to roll things out, a timeline which > begins with trusted directory keys include post-quantum crypto > first, and which ends in enabling clients to use post-quantum >

Re: [tor-dev] Go version in Gitian descriptors

On Sun, Jan 03, 2016 at 11:01:25PM -0600, Jeremy Rand wrote: > I noticed that it looks like Tor Project is using Go 1.4.2 to build > the pluggable transports in Gitian. I'm curious why a newer version > of Go isn't used. My understanding is that Go 1.4.2 (or earlier) is > needed to build Go 1.5

[tor-dev] Go version in Gitian descriptors

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, I noticed that it looks like Tor Project is using Go 1.4.2 to build the pluggable transports in Gitian. I'm curious why a newer version of Go isn't used. My understanding is that Go 1.4.2 (or earlier) is needed to build Go 1.5 because

Re: [tor-dev] Go version in Gitian descriptors

> On 4 Jan 2016, at 16:14, David Fifield wrote: > > On Sun, Jan 03, 2016 at 11:01:25PM -0600, Jeremy Rand wrote: >> I noticed that it looks like Tor Project is using Go 1.4.2 to build >> the pluggable transports in Gitian. I'm curious why a newer version >> of Go isn't

Re: [tor-dev] Quantum-safe Hybrid handshake for Tor

On Sun, 3 Jan 2016 04:16:17 -0500 grarpamp wrote: > http://safecurves.cr.yp.to/ > > Just another link. None of those algorithms will hold up to a quantum computer, and apart from for TLS (where we use the NIST curves) we already use "safe" Curve/Ed25519. So I don't know why

Re: [tor-dev] Quantum-safe Hybrid handshake for Tor

On Sat, Jan 2, 2016 at 7:11 PM, Jesse V wrote: > Here's a webpage, a paper, and software from djb: > http://sphincs.cr.yp.to/ This is of course one example, there are other > works on [typeof] cryptography, and I'm sure most of the authors > like to provide a reference

Re: [tor-dev] Quantum-safe Hybrid handshake for Tor

On Sat, Jan 2, 2016 at 10:22 PM, Yawning Angel wrote: > In terms of prioritization, ensuring all existing traffic isn't > subject to later decryption is far more important I'd think so as you could adapt around other things, but a traffic decrypt seems quite bad,

Re: [tor-dev] Comparing Stem, metrics-lib, and zoossh

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Damian, I'm digging out this old thread, because I think it's still relevant. I started writing some performance evaluations for metrics-lib and got some early results. All examples read a monthly tarball from CollecTor and do something trivial