Live data from Hacker News

Some gripes about nacl

tedunangst.com

11–20 of 47 posts

Re: Some gripes about nacl

#13
post #8

[deleted]

Please read the article more carefully. The article assumes the reader knows what NaCL is and does not explain it, but it's easy to infer he doesn't talk about the Google native client technology, but about something else.

NaCL: http://nacl.cr.yp.to/

Native client: https://code.google.com/p/nativeclient/

Re: Some gripes about nacl

#14
post #6
post #5

Simply put, use the reference nacl implementation only when you really know what you're doing. As with all things crypto it's easy to shoot yourself in the foot, and libsodium makes it a bit harder than reference nacl.

Though the first sentence of the NaCL website says: "NaCl (pronounced "salt") is a new easy-to-use high-speed software library"...

I suppose easy is a relative term here.

Re: Some gripes about nacl

#15
Isn't the fact that nacl is written by such highly reputable guy(in the crypto community) and that it sees relatively lots of review by experts important here ?

Re: Some gripes about nacl

#16
post #11

This title a very subtle trap for those who do not read articles. :P

It's amazing how people can comment without reading the article. It's obvious this happens to some degree, but I was amazed that the first few posts in this thread have exclusively been about a completely different thing.

Re: Some gripes about nacl

#18
post #16
post #11

This title a very subtle trap for those who do not read articles. :P

It's amazing how people can comment without reading the article. It's obvious this happens to some degree, but I was amazed that the first few posts in this thread have exclusively been about a completely different thing.

The 3rd and 4th comments were on topic. Now half the comments are boring meta discussion of the confusion.

Re: Some gripes about nacl

#19
Somehow these and other "gripes" about djb software over the years have never been as interesting or entertaining as the ones djb himself has been sharing with us since the 90's. But complaints are to be expected.

Personally I do not care for libsodium, but to each his own.

Instead I chose to study curveprotect, tinysshd (tweetnacl), qremote, etc. as examples to learn from. Realizing that everyone is capable of making mistakes, but some are less likely than others.

Post reply on HN