diff options
author | Brent Cook <bcook@openbsd.org> | 2014-10-14 22:51:02 -0500 |
---|---|---|
committer | Brent Cook <bcook@openbsd.org> | 2014-10-15 16:36:08 -0500 |
commit | a007fb9d5344cb52244d013fd80938a0509e739c (patch) | |
tree | 6cffd07d0d2b8d01e3d9dade28815a5324e5a273 | |
parent | 2408253191b5cdb887041e1c235eaae12b914d1a (diff) | |
download | portable-a007fb9d5344cb52244d013fd80938a0509e739c.tar.gz portable-a007fb9d5344cb52244d013fd80938a0509e739c.tar.bz2 portable-a007fb9d5344cb52244d013fd80938a0509e739c.zip |
LibreSSL portable README update
Add more info on how to build from source, where to download it from.
-rw-r--r-- | README | 52 |
1 files changed, 34 insertions, 18 deletions
@@ -1,34 +1,50 @@ | |||
1 | This package is the official portable version of LibreSSL | 1 | This package is the official portable version of LibreSSL |
2 | (http://www.libressl.org). | 2 | (http://www.libressl.org). |
3 | 3 | ||
4 | LibreSSL is a fork of OpenSSL developed by the OpenBSD project | 4 | LibreSSL is a fork of OpenSSL developed by the OpenBSD project |
5 | (http://www.openbsd.org). LibreSSL is developed on OpenBSD. This | 5 | (http://www.openbsd.org). LibreSSL is developed on OpenBSD. This |
6 | package then adds portability shims for other operating systems. | 6 | package then adds portability shims for other operating systems. |
7 | 7 | ||
8 | Official release tarballs are available at your friendly neighborhood | 8 | Official release tarballs are available at your friendly neighborhood |
9 | OpenBSD mirror in directory LibreSSL, e.g.: | 9 | OpenBSD mirror in directory LibreSSL, e.g.: |
10 | http://ftp.openbsd.org/pub/OpenBSD/LibreSSL/ | ||
11 | although it is suggested you use a mirror. | ||
12 | 10 | ||
13 | Development is done in the upstream OpenBSD codebase. A github clone | 11 | http://ftp.openbsd.org/pub/OpenBSD/LibreSSL/ |
14 | of the official repositories is kept at: | ||
15 | https://github.com/libressl-portable | ||
16 | We update this repository from the OpenBSD respositories | ||
17 | semi-frequently, so changes may not show up in GitHub immediately. | ||
18 | The GitHub repository should be used for informational purposes | ||
19 | only. | ||
20 | 12 | ||
21 | ./configure && make check && make install | 13 | although we suggest that you use a mirror: |
22 | 14 | ||
23 | See crypto/compat for the bulk of the local compatibility code. | 15 | http://www.openbsd.org/ftp.html |
24 | 16 | ||
25 | It will likely build on any reasonably modern version of Linux, Solaris, | 17 | The LibreSSL portable build framework is also mirrored in Github: |
26 | or OSX with a sane compiler and C library. | 18 | |
19 | https://github.com/libressl-portable/portable | ||
20 | |||
21 | If you have checked this source using Git, follow these initial steps to | ||
22 | prepare the source tree for building: | ||
23 | |||
24 | 1. ensure you have the following packages installed: | ||
25 | automake, autoconf, bash, git, libtool, perl, pod2man | ||
26 | 2. run './autogen.sh' to prepare the source tree for building | ||
27 | or run './dist.sh' to prepare a tarball. | ||
28 | |||
29 | Once you have a source tree from Git or FTP, run these commands to build and | ||
30 | install the package: | ||
31 | |||
32 | ./configure # see ./configure --help for configuration options | ||
33 | make check # runs builtin unit tests | ||
34 | make install # set DESTDIR= to install to an alternate location | ||
35 | |||
36 | The resulting library and 'openssl' utility is largely API-compatible with | ||
37 | OpenSSL 1.0.1. However, it is not ABI compatible - you will need to relink your | ||
38 | programs to LibreSSL in order to use it, just as in moving from OpenSSL 0.9.8 | ||
39 | to 1.0.1. | ||
40 | |||
41 | LibreSSL portable will likely build on any reasonably modern version of Linux, | ||
42 | Solaris, or OSX with a standards-compliant compiler and C library. If you are | ||
43 | working a new port, most of the OS-specific compatibility code is found in | ||
44 | 'crypto/compat' | ||
27 | 45 | ||
28 | Note: Our policy is generally to use your system provided intrinsics. | 46 | Note: Our policy is generally to use your system provided intrinsics. |
29 | If your system provides security sensitive functions (such as | 47 | If your system provides security sensitive functions (such as |
30 | arc4random(), issetugid(), calloc(), getentropy(), and others) we will | 48 | arc4random(), issetugid(), calloc(), getentropy(), and others) we will |
31 | assume they are implemented correctly and securely. If they are | 49 | assume they are implemented correctly and securely. If they are |
32 | not please contact your OS provider. | 50 | not please contact your OS provider. |
33 | |||
34 | |||