update README to reflect current porting approach
ok beck@ deraadt@
This commit is contained in:
parent
1c5591947a
commit
e864776f0b
14
README
14
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
|
programs to LibreSSL in order to use it, just as in moving from OpenSSL 0.9.8
|
||||||
to 1.0.1.
|
to 1.0.1.
|
||||||
|
|
||||||
LibreSSL portable will likely build on any reasonably modern version of Linux,
|
The project attempts to provide working alternatives for operating systems with
|
||||||
Solaris, or OSX with a standards-compliant compiler and C library. If you are
|
limited or broken security primitives (e.g. arc4random(3), issetugid(2)) and
|
||||||
working a new port, most of the OS-specific compatibility code is found in
|
assists with improving OS-native implementations where possible.
|
||||||
'crypto/compat'
|
|
||||||
|
|
||||||
Note: Our policy is generally to use your system provided intrinsics.
|
LibreSSL portable will build on any reasonably modern version of Linux,
|
||||||
If your system provides security sensitive functions (such as
|
Solaris, or OSX with a standards-compliant compiler and C library.
|
||||||
arc4random(), issetugid(), calloc(), getentropy(), and others) we will
|
|
||||||
assume they are implemented correctly and securely. If they are
|
|
||||||
not please contact your OS provider.
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user