Re:Introducing Sodium, a new cryptographic library
by tptacek on Wednesday March 06, 2013 @07:53PM
(#5335193)
DJB's NaCL is an academic project that dates at least back to 2008.
Re:Introducing Sodium, a new cryptographic library
by apaprocki on Wednesday March 06, 2013 @08:55PM
(#5335454)
I'm just lamenting to no one in particular that in the universe of available words/acronyms/abbreviations to describe projects we have as many collisions as we do. If I had to choose (ugh), DJB's NaCL acronym is at least more specific to its purpose than NaCl meaning "Native Client" just to make a salt + pepper pun. I guess all I'm saying is that if I ever write an open-source slab allocator, I won't call it OpenSSl.
Re:Introducing Sodium, a new cryptographic library
by tptacek on Wednesday March 06, 2013 @09:26PM
(#5335618)
Of course not. You'd call it "6 Minute Slabs".
Re:Introducing Sodium, a new cryptographic library
by bascule on Wednesday March 06, 2013 @10:06PM
(#5335788)
djb's NaCl and Google's NaCl appeared around the same time. The naming conflict is unfortunate, but it happens.
Hopefully Sodium doesn't suffer from the same namespace collision.
Re:Introducing Sodium, a new cryptographic library
by bathat on Wednesday March 06, 2013 @11:20PM
(#5336059)
It's not quite as bad as Maxima (http://en.wikipedia.org/wiki/Maxima_%28software%29), though, where it almost feels like the project was intentionally named in a way to make googling difficult.
Re:Introducing Sodium, a new cryptographic library
by newman314 on Thursday March 07, 2013 @12:42AM
(#5336315)
Like Go?
Re:Introducing Sodium, a new cryptographic library
by qznc on Thursday March 07, 2013 @01:48AM
(#5336483)
C, D, R, Io, ...
Most single letters are taken for programming languages. http://en.wikipedia.org/wiki/List_of_programming_languages
This: NaCL + Sodium
Google: NaCl (Native Client) + Pepper