News for hackers. Stuff that matters.
Re:Cryptographic Libraries by tptacek on Thursday October 29, 2015 @05:09PM (#10474311)
Don't use these libraries for new cryptosystems. They're low-level, and so very easy to get wrong. And the primitives they expose are mostly outmoded. Your code will be safer, your crypto will be stronger, and your website will look cooler if you can tell people you used Nacl/libsodium instead of Common Crypto.
Re:Cryptographic Libraries by FredericJ on Thursday October 29, 2015 @05:20PM (#10474392)
Isn't it ironic to see so much inline assembly while Apple is telling third party devs that they can't distribute binaries on WatchOS and that iOS apps are moving towards Bitcode too?

Apple's crypto people definitely know that assembly is key in performance and side-channel resistance of cryptographic implementations. They use it constantly. I guess at some point they will just ask 3rd party devs to call corecrypto methods if they want to use encryption in Bitcode apps.

But this means that you'll have to wait for Apple to implement whatever primitive you need for your app. Good enough in most cases but encryption apps with special needs will find this annoying.

Re:Cryptographic Libraries by tptacek on Thursday October 29, 2015 @06:19PM (#10474781)
So far as I can tell, libsodium works on iOS.

Don't write crypto for watches, is what I think.