On Apr 28, 2017, at 5:03 PM, Tony Garnock-Jones wrote: > Hi James, > > On 4/28/17 1:13 PM, James wrote: >> https://github.com/mgorlick/CRESTaceans/tree/master/bindings/libsodium >> https://github.com/tonyg/racl/tree/master > > I'm the author of racl. I've not used mgorlick's code, but one thing to > bear in mind is that it uses libsodium, where racl uses plain NaCl. > Libsodium is definitely the way to go - plain NaCl is largely vestigial > at this point. > > If I were to use racl in production, I would change the implementation > of racl to use libsodium instead of NaCl.
Thanks that's really helpful. I had heard that libsodium was the way to go but I'm just now reading about the details. > > Racl includes a few useful utilities (like SPKI SEXP I/O and some hacky > sketches of encrypted TCP ports based on NaCl primitives), where > mgorlick's code looks to be just the NaCl primitives. > > mgorlick's code has contracts; mine does not, which is a shame. I should > add some. > > Finally, neither NaCl nor libsodium nor racl provides anything TLS-like. > If you wanted some kind of streaming network code on top of NaCl, you're > firmly in "roll-your-own crypto" territory. I think we want standard TLS. I know enough about cryptography to know that I really don't want to roll my own. So I guess OpenSSL is what we'll use but then, maybe, something else for local file cryptography and signing. We might even use OpenPGP as a helper application. James -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
