cryb.to/cryb-to
1
0
Fork 0
mirror of https://github.com/cryb-to/cryb-to.git synced 2024-11-26 07:35:45 +00:00
Code Issues Projects Releases Packages Wiki Activity
The Cryb libraries
257 commits 36 branches 15 tags 1.2 MiB
C 94.8%
Roff 3.1%
M4 1.1%
Makefile 0.7%
C++ 0.2%
Find a file
Dag-Erling Smørgrav 09ce719dd8 Clean up and re-add gcc.
2016-09-18 21:24:39 +02:00
include Bump version. 2016-09-18 21:22:58 +02:00
lib Don't call string_expand() unless we know that we need to. 2016-09-17 23:42:09 +02:00
m4 Add support for __builtin_bswap16. 2016-09-15 11:09:34 +02:00
t Add test cases for the new string functions. 2016-09-17 23:32:11 +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 Clean up and re-add gcc. 2016-09-18 21:24:39 +02:00
autogen.des Respect user's CC 2016-09-04 16:18:13 +02:00
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 typo 2015-12-14 16:05:18 +01:00
README.md Prepare for moving to Github 2015-12-14 15:55:38 +01:00
RELNOTES

README.md

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.