News for hackers. Stuff that matters.
Re:Introducing Sodium, a new cryptographic library by newman314 on Wednesday March 06, 2013 @09:14PM (#5335539)
Next step, openssh ported to use Sodium as an alternative?
Re:Introducing Sodium, a new cryptographic library by tptacek on Wednesday March 06, 2013 @09:51PM (#5335727)
SSH is a good example of the kind of thing that can't use high-level crypto libraries, because the constructions required to implement SSH are part of the specification.

We're all waiting for Daniel Bernstein to replace SSH, but it hasn't happened yet.

Re:Introducing Sodium, a new cryptographic library by jedisct1 on Thursday March 07, 2013 @12:15AM (#5336236)
Do we need a replacement for SSH? The OpenSSH team is doing an amazing work. Besides making the tool as secure as possible, they are also improving the protocol. The recently added support for encrypt-then-MAC modes is a great step forward.
Re:Introducing Sodium, a new cryptographic library by tptacek on Thursday March 07, 2013 @12:18AM (#5336243)
I have a lot of respect for the OpenSSH team but think that they are saddled with a protocol that was designed (a) before anyone had a good idea how to design resilient cryptographic transports and (b) without a clear understanding of how people would want remote control channels to work in 2013.