a5c82283e0
If an OS provides an arc4random_buf implementation in its C library, prefer it over an in-library version. This allows OS-specific implementations to become more robust over time. It also prevents possible link-time confusion as to which arc4random_buf implementation is in use by an application when linked with LibreSSL. The built-in unit tests will identify some common issues, such as fork safety and PID wrap handling. Other elements, such as seeding mechanisms, should be audited by the vendor or user for correctness. ok deraadt@ beck@ |
||
---|---|---|
apps | ||
crypto | ||
include | ||
man | ||
ssl | ||
tests | ||
.gitignore | ||
AUTHORS | ||
autogen.sh | ||
configure.ac.tpl | ||
libcrypto.pc.in | ||
libressl.pub | ||
libssl.pc.in | ||
Makefile.am | ||
Makefile.am.common | ||
NEWS | ||
openssl.pc.in | ||
README | ||
update.sh | ||
VERSION |
This package is the official portable version of LibreSSL (http://www.libressl.org). LibreSSL is a fork of OpenSSL developed by the OpenBSD project (http://www.openbsd.org). LibreSSL is developed on OpenBSD. This package then adds portability shims for other operating systems. Official release tarballs are available at your friendly neighborhood OpenBSD mirror in directory LibreSSL, e.g.: http://ftp.openbsd.org/pub/OpenBSD/LibreSSL/ although it is suggested you use a mirror. Development is done in the upstream OpenBSD codebase. A github clone of the official repositories is kept at: https://github.com/libressl-portable We update this repository from the OpenBSD respositories semi-frequently, so changes may not show up in GitHub immediately. The GitHub repository should be used for informational purposes only. ./configure && make check && make install See crypto/compat for the bulk of the local compatibility code. It will likely build on any reasonably modern version of Linux, Solaris, or OSX with a sane compiler and C library. Note: Our policy is generally to use your system provided intrinsics. If your system provides security sensitive functions (such as arc4random(), issetugid(), calloc(), getentropy(), and others) we will assume they are implemented correctly and securely. If they are not please contact your OS provider.