The Cryb libraries
Find a file
Dag-Erling Smørgrav 304fc8314d Solve further asprintf() issues by sweeping them under the rug.
All further instances of asprintf() or vasprintf() in our codebase are either in libcryb-test or in individual unit tests, and in all cases, the only consequence of a failed call is that the result will say "no description" instead of either a description of the test or an explanation of how it failed.  Therefore, we can simply ignore the problem and cast the call to void to satisfy gcc.
2016-09-18 22:40:48 +02:00
include Bump version. 2016-09-18 21:22:58 +02:00
lib Solve further asprintf() issues by sweeping them under the rug. 2016-09-18 22:40:48 +02:00
m4 Add support for __builtin_bswap16. 2016-09-15 11:09:34 +02:00
t Solve further asprintf() issues by sweeping them under the rug. 2016-09-18 22:40:48 +02:00
tools Centralize most of .gitignore. 2016-09-17 21:38:54 +02:00
.gitignore Centralize most of .gitignore. 2016-09-17 21:38:54 +02:00
.travis.yml Correct YAML. 2016-09-18 21:37:52 +02:00
autogen.des
autogen.sh
configure.ac Add wide-character versions of strlcat(), strlcmp(), strlcpy(). 2016-09-17 21:35:42 +02:00
CREDITS
HISTORY
INSTALL
LICENSE
Makefile.am
mkpkgng.in
README
README.md
RELNOTES

The Cryb libraries

The Cryb libraries are a collection of cryptography- and security-related function libraries written with the following goals in mind:

  • Comprehensive: Cryb aims to provide a rich and flexible set of building blocks for cryptographic applications.

  • Self-contained and easily embeddable: the Cryb libraries have no external dependencies (apart from the toolchain) and few internal ones. Individual modules and algorithms can easily be extracted from Cryb and integrated into other codebases.

  • Reliable: the libraries come with an extensive test suite with a long-term goal of 100% test coverage.

  • Stable: guaranteed API and ABI stability.

  • Documented: full API documentation in the form of Unix man pages.

  • Consistently and permissively licensed: the entire collection is under the 3-clause BSD license.

Caveat

We aren't there yet. The Cryb libraries are still undeniably at the experimental stage. However, significant portions are already in production use as components in other projects (cf: easily embeddable), and we have great expectations for the future of Cryb.