aws-lc mit Homebrew, apk, Nix, zypper installieren

Projektlinks

• Homepage
• Upstream-Dokumentation
• Paketmanager-Seite

Befehle und Aliase

• bssl
• c_rehash

Projektgeschichte

The project presents itself as maintained by the AWS Cryptography team and explicitly traces its code lineage to Google's BoringSSL and OpenSSL. Its git history preserves older imported upstream commits, but AWS-specific work appears in 2020, with early tags such as v0.1-alpha and v0.1-beta in September 2020.

AWS-LC's stated goal is to maintain a secure libcrypto compatible with software and applications used at AWS, while also giving the AWS Cryptography team a public home for open-source cryptographic contributions and enhancements.

Adoptionsgeschichte

AWS-LC is aimed at infrastructure and language/runtime consumers that need an OpenSSL-like API surface, tuned implementations, FIPS work, and CI coverage across AWS-relevant platforms. Its Homebrew formula also exposes command-line utilities such as bssl and c_rehash for developers who want the library toolchain locally.

Package-manager adoption matters here because replacing or supplementing OpenSSL-family libraries is operationally sensitive: downstream packages care about ABI/API compatibility, FIPS status, CPU optimizations, and whether the library is available through system package channels.

Wie es verwendet wird

Typical use is as a build dependency or embedded TLS/crypto provider. The README points users to BUILDING.md for dependencies and build options, public headers for API documentation, PORTING.md for OpenSSL migration, and FIPS.md for FIPS-specific builds.

AWS-LC includes portable C implementations plus optimized assembly for selected x86 and Arm processors, and documents supported platforms including Linux, macOS, Windows, Android, and iOS.

Warum Paket-Nerds sich dafür interessieren

For package maintainers, AWS-LC is interesting because it sits in the BoringSSL/OpenSSL family but is packaged as an AWS-maintained crypto library with formal verification references, FIPS artifacts, and active cross-platform CI. That makes the formula more like infrastructure plumbing than a standalone app.

Zeitleiste

• 2020: AWS-specific AWS-LC commits and alpha/beta tags appear in the public repository.
• 2021: v0.0.1 and FIPS-related tags appear.
• 2022: v1.x releases continue alongside AWS-LC-FIPS tags.
• 2026: v5.x tags show the project remains actively released.

Related projects

• BoringSSL and OpenSSL are the stated code bases AWS-LC is based on.
• AWS-LC Formal Verification and s2n-bignum are referenced by the README for verified cryptographic code paths.

Quellen

• https://github.com/aws/aws-lc#readme
• https://github.com/aws/aws-lc/blob/main/BUILDING.md
• https://github.com/aws/aws-lc/blob/main/PORTING.md
• https://github.com/aws/aws-lc/blob/main/crypto/fipsmodule/FIPS.md
• official git history and tags from https://github.com/aws/aws-lc