Frank Denis
6ac18dae42
Projects using the legacy API are unlikely to use these new macros. OTOH, people using the Sodium API would be puzzled about the missing 16 bytes in the secretbox and box APIs. More importantly, these macros are designed for bindings. Having these bindings enforce proper limits (for the *_easy API that they all use) and yet have the underlying library call sodium_misuse() would be sad.
Sodium is a new, easy-to-use software library for encryption, decryption, signatures, password hashing and more.
It is a portable, cross-compilable, installable, packageable fork of NaCl, with a compatible API, and an extended API to improve usability even further.
Its goal is to provide all of the core operations needed to build higher-level cryptographic tools.
Sodium supports a variety of compilers and operating systems, including Windows (with MingW or Visual Studio, x86 and x64), iOS and Android.
Documentation
The documentation is a work-in-progress, and is being written using Gitbook:
- libsodium documentation - online, requires Javascript.
- offline documentation in PDF, MOBI and ePUB formats.
Integrity Checking
The integrity checking instructions (including the signing key for libsodium) are available in the installation section of the documentation.
Community
A mailing-list is available to discuss libsodium.
In order to join, just send a random mail to sodium-subscribe {at}
pureftpd {dot} org.