[openssh-commits] [openssh] 04/04: Add AWS-LC and BoringSSL as potential libcryptos.

[git+noreply at mindrot.org]

This is an automated email from the git hooks/post-receive script.

dtucker pushed a commit to branch master
in repository openssh.

commit acf749756872d7555eca48514e5aca6962116fb2
Author: Darren Tucker <dtucker at dtucker.net>
AuthorDate: Tue Feb 24 11:28:11 2026 -0500

    Add AWS-LC and BoringSSL as potential libcryptos.
---
 INSTALL   | 9 ++++++---
 README.md | 2 +-
 2 files changed, 7 insertions(+), 4 deletions(-)

diff --git a/INSTALL b/INSTALL
index 56e351af6..96b299477 100644
--- a/INSTALL
+++ b/INSTALL
@@ -19,12 +19,15 @@ A working installation of zlib:
 Zlib 1.1.4 or 1.2.1.2 or greater (earlier 1.2.x versions have problems):
 https://zlib.net/
 
-libcrypto from either of LibreSSL or OpenSSL.  Building without libcrypto
-is supported but severely restricts the available ciphers and algorithms.
+libcrypto from one of LibreSSL, OpenSSL, AWS-LC or BoringSSL.  Building
+without libcrypto is supported but severely restricts the available
+ciphers and algorithms.
  - LibreSSL (https://www.libressl.org/) 3.1.0 or greater
  - OpenSSL (https://www.openssl.org) 1.1.1 or greater
+ - AWS-LC (https://github.com/aws/aws-lc)
+ - BoringSSL (https://github.com/google/boringssl)
 
-LibreSSL/OpenSSL should be compiled as a position-independent library
+libcrypto should be compiled as a position-independent library
 (i.e. -fPIC, eg by configuring OpenSSL as "./config [options] -fPIC"
 or LibreSSL as "CFLAGS=-fPIC ./configure") otherwise OpenSSH will not
 be able to link with it.  If you must use a non-position-independent
diff --git a/README.md b/README.md
index cf06c3a4e..1cfcd7bb9 100644
--- a/README.md
+++ b/README.md
@@ -34,7 +34,7 @@ Stable release tarballs are available from a number of [download mirrors](https:
 
 Portable OpenSSH is built using autoconf and make. It requires a working C compiler, standard library and headers.
 
-``libcrypto`` from either [LibreSSL](https://www.libressl.org/) or [OpenSSL](https://www.openssl.org) may also be used.  OpenSSH may be built without either of these, but the resulting binaries will have only a subset of the cryptographic algorithms normally available.
+``libcrypto`` from one of [LibreSSL](https://www.libressl.org/), [OpenSSL](https://www.openssl.org), [AWS-LC](https://github.com/aws/aws-lc) or [BoringSSL](https://github.com/google/boringssl) may also be used.  OpenSSH may be built without either of these, but the resulting binaries will have only a subset of the cryptographic algorithms normally available.
 
 [zlib](https://www.zlib.net/) is optional; without it transport compression is not supported.
 

-- 
To stop receiving notification emails like this one, please contact
djm at mindrot.org.