Introducing Sodium, a new cryptographic library

Re:Introducing Sodium, a new cryptographic library by alexjeffrey on Wednesday March 06, 2013 @06:50PM (#5334880)

that's true, but it's the highest-profile encryption drama I could think of - a more appropriate example would probably be the onslaught of companies which are storing passwords in plaintext or simple MD5 hashes.

[ Parent | on HN ]

Re:Introducing Sodium, a new cryptographic library by tptacek on Wednesday March 06, 2013 @06:51PM (#5334891)

Hate to keep doing this to you† but you don't need anything like NaCL to solve that problem; just use bcrypt. Every development environment has a bcrypt.

Good example of a flaw mitigated by NaCL: the CBC padding oracle attack.

† Caveat: no I don't

[ Parent | on HN ]

Re:Introducing Sodium, a new cryptographic library by alexjeffrey on Wednesday March 06, 2013 @06:56PM (#5334926)

OK you caught me - I don't have any relevant examples :)

[ Parent | on HN ]

Re:Introducing Sodium, a new cryptographic library by jedisct1 on Wednesday March 06, 2013 @10:23PM (#5335855)

As pointed out by @bascule, Sodium will ship with the winning function of the Password Hashing Competition.

[ Parent | on HN ]