The Cryb libraries
Find a file
Dag-Erling Smørgrav 2ba5067496 Do not attempt to catch SIGABRT emanating from a test case.
It is reasonable to assume that a SIGABRT originates from a call to abort(3), either directly or via assert(3).  Both the C standard and POSIX give the implementation great latitude with regard to abort(3)'s behavior, and both explicitly mention that it may close all streams before raising SIGABRT.  This means that we cannot safely proceed after a call to abort(3).  One could argue that we can't safely proceed after a SIGBUS or SIGSEGV either, but in practice, the damage is usually quite limited.
2016-11-14 12:59:13 +01:00
include Constify t_compare_ptr(). 2016-10-03 16:55:27 +02:00
lib Do not attempt to catch SIGABRT emanating from a test case. 2016-11-14 12:59:13 +01: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 Ignore editor droppings. 2016-11-14 12:59:13 +01:00
.travis.yml Correct YAML. 2016-09-18 21:37:52 +02:00
autogen.des Respect user's CC 2016-09-04 16:18:13 +02:00
autogen.sh
configure.ac Alphabetize. 2016-11-14 12:59:13 +01:00
CREDITS Differentiate between the Cryb libraries and the Cryb.to project. 2014-12-20 00:47:21 +00:00
HISTORY
INSTALL
LICENSE Correct copyright ranges 2015-12-14 15:55:04 +01:00
Makefile.am
mkpkgng.in If no SVN version is available, use today's date. 2015-02-15 09:19:25 +00:00
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

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.