From e864776f0bb71366812088102e8f4d8f71408263 Mon Sep 17 00:00:00 2001 From: Brent Cook Date: Mon, 27 Oct 2014 20:00:58 -0500 Subject: update README to reflect current porting approach ok beck@ deraadt@ --- README | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-) diff --git a/README b/README index 0b5b8cd..5de150d 100644 --- a/README +++ b/README @@ -38,13 +38,9 @@ OpenSSL 1.0.1. However, it is not ABI compatible - you will need to relink your programs to LibreSSL in order to use it, just as in moving from OpenSSL 0.9.8 to 1.0.1. -LibreSSL portable will likely build on any reasonably modern version of Linux, -Solaris, or OSX with a standards-compliant compiler and C library. If you are -working a new port, most of the OS-specific compatibility code is found in -'crypto/compat' - -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. +The project attempts to provide working alternatives for operating systems with +limited or broken security primitives (e.g. arc4random(3), issetugid(2)) and +assists with improving OS-native implementations where possible. + +LibreSSL portable will build on any reasonably modern version of Linux, +Solaris, or OSX with a standards-compliant compiler and C library. -- cgit v1.2.3-55-g6feb