brew

libressl mit Homebrew, apk, MacPorts, Nix, pacman, zypper, chocolatey, apt, dnf, scoop, winget installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für libressl in AI-Agent-Workflows.

Installationsbefehl Sicherheitshinweise

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%

brew install libressl

local Homebrew formula metadata

MacPortsverifiziert · 94%

sudo port install libressl

MacPorts ports tree · security/libressl/Portfile · Quelle: api.github.com

Linux

Alpine Linux apkverifiziert · 92%

sudo apk add libressl

Alpine Linux edge package indexes · libressl · Quelle: dl-cdn.alpinelinux.org

Nixverifiziert · 92%

nix profile install nixpkgs#libressl

nixpkgs package indexes · pkgs/by-name/li/libressl/package.nix · Quelle: api.github.com

Arch Linux pacmanverifiziert · 92%

sudo pacman -S libressl

Arch Linux sync databases · libressl · Quelle: geo.mirror.pkgbuild.com

openSUSE zypperverifiziert · 92%

sudo zypper install libressl

openSUSE Tumbleweed package metadata · libressl · Quelle: download.opensuse.org

Debian aptverifiziert · 92%

sudo apt install openssl

Debian stable package indexes · openssl · Quelle: deb.debian.org

Fedora dnfverifiziert · 92%

sudo dnf install openssl

Fedora Rawhide package metadata · openssl · Quelle: dl.fedoraproject.org

Windows

Chocolateyverifiziert · 92%

choco install openssl

Chocolatey community package catalog · openssl · Quelle: community.chocolatey.org

Scoopverifiziert · 92%

scoop install main/openssl

Scoop official bucket manifest trees · bucket/openssl.json · Quelle: api.github.com

Windows Package Managerverifiziert · 92%

winget install --id ShiningLight.OpenSSL.Dev -e

Windows Package Manager source index · ShiningLight.OpenSSL.Dev · Quelle: cdn.winget.microsoft.com

Überblick

Paketzusammenfassung

Version of the SSL/TLS protocol forked from OpenSSL

Projektlinks

Befehle und Aliase

ocspcheck
openssl

Verlauf

Projektgeschichte und Nutzung

LibreSSL is the OpenBSD project's fork of the OpenSSL TLS and crypto stack, started in 2014 with goals of modernization, auditability, security, and OpenBSD-style development practice. It ships libcrypto, libssl, libtls, and command-line utilities such as openssl and ocspcheck.

Projektgeschichte

The official site describes LibreSSL as forked from OpenSSL in 2014, with primary development inside the OpenBSD source tree and regular portable repackaging for other operating systems. The portable repository states the fork point as OpenSSL 1.0.1g and explains that the GitHub project contains the build scaffold and compatibility layer for building OpenBSD's LibreSSL code outside OpenBSD.

The project goals are deliberately conservative: modernize the OpenSSL codebase, apply code review and frequent releases, remove obsolete or broken features and operating-system support, and encourage safer programming interfaces. The portable README also makes clear that LibreSSL is not ABI-compatible with OpenSSL and that API compatibility is limited by the projects' different priorities.

Adoptionsgeschichte

LibreSSL was adopted first as part of OpenBSD and then as a portable package for Linux, BSDs, macOS, Windows, and other systems. Its wider package-manager life has been shaped by a trade-off: users wanted a cleaned-up OpenSSL-compatible stack, but many large ecosystems remained tied to OpenSSL ABI/API expectations.

For Unix distributions and Homebrew, LibreSSL became a useful alternate TLS implementation and a source of the libtls API, while also serving as a practical stress test for software that claimed OpenSSL portability but depended on OpenSSL-specific behavior.

Wie es verwendet wird

Packaged LibreSSL is used either by linking applications to libcrypto, libssl, or libtls, or through command-line tools such as openssl and ocspcheck. The release process tracks OpenBSD development: stable portable branches are derived from OpenBSD releases and receive security updates for a defined support window.

Warum Paket-Nerds sich dafür interessieren

LibreSSL is package-nerd significant because it is a security fork with real downstream consequences. It forces maintainers to separate OpenSSL-the-API from OpenSSL-the-implementation, exposes accidental ABI assumptions, and gives package managers a second TLS stack whose release cadence is tied to OpenBSD rather than the OpenSSL project.

Zeitleiste

2014: LibreSSL forked from OpenSSL.
2014-07-11: LibreSSL 2.0.0 released, based on an OpenBSD 5.6 development snapshot.
2014-08-08: LibreSSL 2.0.5 tied to OpenBSD 5.6 release.
2015-09-23: LibreSSL 2.3.0 released.
2024-10-14: LibreSSL 4.0.0 released.
2026-05-25: LibreSSL 4.3.2 released.

Related projects

Related projects include OpenSSL, OpenBSD's libcrypto/libssl/libtls trees, BoringSSL, AWS-LC, wolfSSL, mbedTLS, and downstream software such as OpenSSH and curl that depend on TLS libraries.

Quellen

Sicherheitslage

Risikostufe: grün

library-like package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

library-like package without higher-risk signals

Signale

metadata:library-like

Installationsverhalten

In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
Installiert mit 1 Laufzeitabhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix: /etc/ssl/openssl.cnf

Executables

Installierte Executables

Befehl	Art	Sichtbarkeit	Hinweis
`ocspcheck`	cli	globales Executable
`openssl`	cli	globales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25

Manager-Version4.3.2

Manager aktualisiert2026-07-05

lokale DatenOK

Upstreamnot checked

neueste erkannte Versionnicht erkannt

Paketschlüssel	brew:libressl
Version	4.3.2
Paketmanager	Homebrew
Paketmanager-Seite	https://formulae.brew.sh/formula/libressl
Homepage	https://www.libressl.org/
Repository	https://github.com/libressl/portable
Upstream-Dokumentation	https://github.com/libressl/portable#readme
Lizenz	OpenSSL
Quellarchiv	https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-4.3.2.tar.gz
Zuletzt aktualisiert	2026-07-05T04:22:04Z
Pulse	updated
Abhängigkeiten	ca-certificates
Bottle	verfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install	nicht definiert
Dienst	keiner deklariert
Einschränkungen	A CA file has been bootstrapped using certificates from the SystemRoots keychain. To add additional certificates (e.g. the certificates added in the System keychain), place .pem files in $HOMEBREW_PREFIX/etc/libressl/certs and run $HOMEBREW_PREFIX/opt/libressl/bin/openssl certhash $HOMEBREW_PREFIX/etc/libressl/certs

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	libressl
Version Scheme	0
Revision	0
Head Version	HEAD
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	yes
URL Keys	head stable