| 1 |
Source: golang-github-caddyserver-certmagic |
| 2 |
Maintainer: Debian Go Packaging Team <[email protected]> |
| 3 |
Uploaders: Peymaneh <[email protected]> |
| 4 |
Section: golang |
| 5 |
Testsuite: autopkgtest-pkg-go |
| 6 |
Priority: optional |
| 7 |
Build-Depends: debhelper-compat (= 13), |
| 8 |
dh-golang, |
| 9 |
golang-any, |
| 10 |
golang-go.uber-zap-dev, |
| 11 |
golang-github-caddyserver-zerossl-dev, |
| 12 |
golang-github-miekg-dns-dev, |
| 13 |
golang-github-libdns-libdns-dev (>= 1.1.1~), |
| 14 |
golang-github-klauspost-cpuid-dev (>= 2.0.6~), |
| 15 |
golang-github-mholt-acmez-v3-dev, |
| 16 |
golang-github-zeebo-blake3-dev, |
| 17 |
golang-golang-x-crypto-dev, |
| 18 |
golang-golang-x-net-dev |
| 19 |
Standards-Version: 4.7.4.1 |
| 20 |
Vcs-Browser: https://salsa.debian.org/go-team/packages/golang-github-caddyserver-certmagic |
| 21 |
Vcs-Git: https://salsa.debian.org/go-team/packages/golang-github-caddyserver-certmagic.git |
| 22 |
Homepage: https://github.com/caddyserver/certmagic |
| 23 |
Rules-Requires-Root: no |
| 24 |
XS-Go-Import-Path: github.com/caddyserver/certmagic |
| 25 |
|
| 26 |
Package: golang-github-caddyserver-certmagic-dev |
| 27 |
Architecture: all |
| 28 |
Depends: golang-go.uber-zap-dev, |
| 29 |
golang-github-caddyserver-zerossl-dev, |
| 30 |
golang-github-miekg-dns-dev, |
| 31 |
golang-github-libdns-libdns-dev, |
| 32 |
golang-github-klauspost-cpuid-dev (>= 2.0.6~), |
| 33 |
golang-github-mholt-acmez-v3-dev, |
| 34 |
golang-github-zeebo-blake3-dev, |
| 35 |
golang-golang-x-crypto-dev, |
| 36 |
golang-golang-x-net-dev, |
| 37 |
${misc:Depends} |
| 38 |
Description: Go library for automatic HTTPS using Let's Encrypt |
| 39 |
With CertMagic, one can add one line to your Go application to serve securely |
| 40 |
over TLS, without ever having to touch certificates. |
| 41 |
. |
| 42 |
Features: |
| 43 |
* Fully automated certificate management including issuance and renewal |
| 44 |
* One-liner, fully managed HTTPS servers |
| 45 |
* HTTP->HTTPS redirects |
| 46 |
* Solves all 3 ACME challenges: HTTP, TLS-ALPN, and DNS |
| 47 |
* Robust error handling of any ACME client |
| 48 |
* All libdns DNS providers work out-of-the-box (https://github.com/libdns) |
| 49 |
* Pluggable storage implementations (default: file system) |
| 50 |
* Wildcard certificates |
| 51 |
* Automatic OCSP stapling |
| 52 |
* Distributed solving of all challenges (works behind load balancers) |
| 53 |
* Supports "on-demand" issuance of certificates |
| 54 |
* Optional event hooks for observation |
| 55 |
* Works with any certificate authority (CA) compliant with |
| 56 |
the ACME specification |
| 57 |
* Certificate revocation |
| 58 |
* Scales to hundreds of thousands of names/certificates per instance |
| 59 |
* Use in conjunction with ones own certificates |