16179b87f3
*_BYTES_MAX constants constants represent the maximum size of a message. No accessor functions for now. They will be renamed, as the *_BYTES_MAX suffix was previously also used for the maximum output size of stream ciphers. These macros are designed to be used by language bindings, so they can perform some sanity checks before calling the sodium API. |
||
---|---|---|
builds | ||
contrib | ||
dist-build | ||
m4 | ||
msvc-scripts | ||
packaging | ||
src | ||
test | ||
.gitignore | ||
.travis.yml | ||
appveyor.yml | ||
AUTHORS | ||
autogen.sh | ||
ChangeLog | ||
configure.ac | ||
libsodium-uninstalled.pc.in | ||
libsodium.pc.in | ||
libsodium.sln | ||
libsodium.vcxproj | ||
libsodium.vcxproj.filters | ||
LICENSE | ||
logo.png | ||
Makefile.am | ||
README.markdown | ||
THANKS |
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
.