7237f68d58
Only makes sense to use TLS when linking from a crypto-related library. Had to change the libsodium documentation link a bit because the original URL returns the gitbook.org certificate. cr.yp.to doesn't actually support encrypting HTTP with TLS so we leave it as-is.
37 lines
1.2 KiB
Markdown
37 lines
1.2 KiB
Markdown
[](https://travis-ci.org/jedisct1/libsodium?branch=master)
|
|
[](https://scan.coverity.com/projects/2397)
|
|
|
|
|
|
============
|
|
|
|
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](http://nacl.cr.yp.to/), 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](https://download.libsodium.org/doc/)
|
|
|
|
## 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`.
|
|
|
|
## License
|
|
|
|
[ISC license](https://en.wikipedia.org/wiki/ISC_license).
|