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

Projektlinks

• Homepage
• Repository

Befehle und Aliase

• lego

Projektgeschichte

The project began in 2015, before Let's Encrypt's public beta and before ACME became an RFC. A maintainer discussion explains that lego started around the need to make HTTPS automatic in a Go web-server project, at a time when Certbot still had a different name and ACME client tooling was experimental.

Lego evolved into both a command-line client and an embeddable Go library. Its docs emphasize support for ACME v2/RFC 8555, multiple ACME servers, HTTP-01, DNS-01, TLS-ALPN-01, DNS-PERSIST-01, wildcard and SAN certificates, and a large DNS-provider integration matrix.

Adoptionsgeschichte

Lego's package-manager adoption is broad because certificate automation needs simple deployment on servers, containers, NAS devices, and CI hosts. The Homebrew, Debian, Ubuntu, Alpine, Arch, MacPorts, Nix, Scoop, winget, and zypper package presence in the input mirrors that role: it is a practical infrastructure binary rather than a language-only library.

Wie es verwendet wird

Users commonly call `lego run` or `lego renew` with an email, domains, and a challenge method. DNS-01 support is especially important for wildcard certificates and machines that cannot expose HTTP challenges; the docs maintain per-provider credential and environment-variable pages for that integration surface.

Warum Paket-Nerds sich dafür interessieren

Lego is package-nerd significant because it turned the messy edge of ACME automation into a portable Go binary with hundreds of provider integrations. It also became a library substrate for other Go programs that wanted certificate automation without shelling out to Certbot.

Zeitleiste

• 2015: The project started before Let's Encrypt's public beta.
• 2015-12-03: Dependency metadata records lego v0.1.0.
• 2019-03: RFC 8555 standardized ACME v2.
• 2024-09-05: The project disclosed GHSA-q82r-2j7m-9rv4 for HTTPS enforcement in ACME API use.
• 2026-05: Official docs listed more than 200 DNS providers.

Related projects

• Related ACME clients include Certbot, acme.sh, dehydrated, Caddy's automatic HTTPS stack, Traefik's ACME support, win-acme, and Boulder, the Let's Encrypt CA software. Related standards include ACME RFC 8555 and challenge specifications such as HTTP-01, DNS-01, and TLS-ALPN-01.

Quellen

• https://deps.dev/go/github.com%2Fgo-acme%2Flego/v2.7.2%2Bincompatible
• https://github.com/advisories/GHSA-q82r-2j7m-9rv4
• https://github.com/go-acme/lego
• https://github.com/go-acme/lego/discussions/1914
• https://github.com/go-acme/lego/releases
• https://go-acme.github.io/lego/
• https://go-acme.github.io/lego/dns/
• https://www.rfc-editor.org/rfc/rfc8555