News for hackers. Stuff that matters.
Re:Libsodium 1.0.0 released by nly on Wednesday September 24, 2014 @06:22PM (#8364512)
> It's better if you don't build crypto directly into your application at all, because you can still screw things up even if you build on Nacl.

Nacl was built to provide an API that is incredibly hard to screw up. That was one of djbs primary motivations. If you just need asymmetric encryption, or signing, or hashing, then it's the bees knees. These broad concepts aren't difficult to comprehend, and every developer should strive to understand and be able to use them. We shouldn't be encouraging people to be afraid... especially when things like dumb, plaintext username and password authentication is routinely implemented by developers without a second thought already.

Re:Libsodium 1.0.0 released by tptacek on Wednesday September 24, 2014 @07:51PM (#8364807)
Nacl makes it hard to screw up the constructions. It doesn't make it hard to make invalid assumptions about what a signed encrypted blob actually means.
Re:Libsodium 1.0.0 released by illumen on Thursday September 25, 2014 @06:53AM (#8366507)
+ makes it easy to add two numbers. It doesn't make it hard to make invalid assumptions about what adding two numbers together actually means.
Re:Libsodium 1.0.0 released by tptacek on Thursday September 25, 2014 @09:20AM (#8366924)
Nacl is a good thing. But crypto is just a tool. It's not a magic wand. People have already built vulnerable systems by making bogus assumptions about what Nacl can do.
Re:Libsodium 1.0.0 released by sarciszewski on Sunday September 28, 2014 @01:00AM (#8378974)
That's a shame :(