Hacker News Reader

Comment by alexjeffrey | Hacker News Reader

In what way is NaCL difficult to integrate into existing dev environments? I've not personally used it before, but I've been looking for a library that abstracts away some of the difficulty of cryptography (granted you can't hide it all) and NaCL appears to label itself as such.

View on HN

C library with no bindings that won't trivially† build on Windows: dead on arrival.

† Definitions of "trivial" including "not requiring understanding any of the details of a Unix toolchain at any stage of adoption"

that's a crying shame - the world needs a secure-by-default and easy-to-use crypto library. Someday...

You might be interested in receiving my newsletter; it's called "the world needs a secure-by-default and easy-to-use crypto library". :)

You might want to subtitle it but x is not it.

I just looked at NaCL. It only works if both sides use it, but data at rest isn't the big problem. Servers are.

And this doesn't work if you want to make a replacement for ssh.

Are you just repeating words you found elsewhere in the thread? You'll be hard pressed to find a crypto system that doesn't require implementations at both ends. NaCL is the library used to implement DNSCrypt, which is pretty much ssh for your DNS queries.

That's the goal of Sodium. It builds on Windows.

Any details?

I don't see anything in a Github repo to support this, not with the Microsoft tools. Perhaps it builds under Cygwin and similar, but that's hardly qualifies as "builds on Windows" for practical purposes.

Build scripts for iOS, Android and Windows (using MingW under MSYS):

https://github.com/jedisct1/libsodium/tree/master/dist-build

The end result on Windows is a native DLL library.

Thanks, I see. Any plans to add static lib generation for Microsoft tools (an nmake script) or is there some gcc-isms in the code? DLLs aren't exactly the most desirable arrangement in a heck of a lot of cases.

Reply on news.ycombinator.com