| 1 |
Source: lacme |
| 2 |
Section: utils |
| 3 |
Priority: optional |
| 4 |
Maintainer: Guilhem Moulin <[email protected]> |
| 5 |
Build-Depends: debhelper-compat (= 13), jq, pandoc (>= 2.1~) |
| 6 |
Rules-Requires-Root: no |
| 7 |
Standards-Version: 4.7.0 |
| 8 |
Homepage: https://git.guilhem.org/lacme/about/ |
| 9 |
Vcs-Git: https://salsa.debian.org/debian/lacme.git -b debian/latest |
| 10 |
Vcs-Browser: https://salsa.debian.org/debian/lacme |
| 11 |
|
| 12 |
Package: lacme |
| 13 |
Architecture: all |
| 14 |
Depends: adduser, |
| 15 |
libconfig-tiny-perl, |
| 16 |
libjson-perl, |
| 17 |
libnet-ssleay-perl, |
| 18 |
libtimedate-perl, |
| 19 |
libwww-perl, |
| 20 |
openssl (>= 1.1.0~), |
| 21 |
${misc:Depends}, |
| 22 |
${perl:Depends} |
| 23 |
Recommends: lacme-accountd (>= 0.8.0), liblwp-protocol-https-perl |
| 24 |
Description: ACME client written with process isolation and minimal privileges in mind |
| 25 |
lacme is an ACME client which can be used to request X.509 certificates from |
| 26 |
ACME service providers such as Let's Encrypt or ZeroSSL. The architecture is |
| 27 |
divided into four components, each with its own executable: |
| 28 |
. |
| 29 |
* A process to manage the account key and issue SHA-256 signatures needed for |
| 30 |
each ACME command. (This process binds to a UNIX-domain socket to reply to |
| 31 |
signature requests from the ACME client.) One can use the UNIX-domain |
| 32 |
socket forwarding facility of OpenSSH 6.7 and later to run this process on |
| 33 |
a different host. |
| 34 |
. |
| 35 |
* A "master" process, which runs as root and is the only component |
| 36 |
with access to the private key material of the server keys. It is used to |
| 37 |
fork the ACME client (and optionally the ACME webserver) after dropping |
| 38 |
root privileges. For certificate issuances, it also generates Certificate |
| 39 |
Signing Requests, then verifies the validity of the issued certificate, and |
| 40 |
optionally reloads or restarts services. |
| 41 |
. |
| 42 |
* An actual ACME client, which builds ACME commands and dialogues with |
| 43 |
the remote ACME server. Since ACME commands need to be signed with the |
| 44 |
account key, the "master" process passes the UNIX-domain socket of the |
| 45 |
account key manager to the ACME client: data signatures are requested by |
| 46 |
writing the data to be signed to the socket. |
| 47 |
. |
| 48 |
* For certificate issuances, an optional webserver, which is spawned |
| 49 |
by the "master" process when no service is listening on the HTTP port. |
| 50 |
(The only challenge type currently supported is "http-01", which requires a |
| 51 |
webserver to answer challenges.) That webserver only processes GET and |
| 52 |
HEAD requests under the "/.well-known/acme-challenge/" URI. By default |
| 53 |
some iptables(8) rules are automatically installed to open the HTTP port, |
| 54 |
and removed afterwards. |
| 55 |
|
| 56 |
Package: lacme-accountd |
| 57 |
Architecture: all |
| 58 |
Depends: libconfig-tiny-perl, libjson-perl, ${misc:Depends}, ${perl:Depends} |
| 59 |
Recommends: libcrypt-openssl-rsa-perl |
| 60 |
Suggests: gpg, openssl |
| 61 |
Multi-Arch: foreign |
| 62 |
Description: lacme account key manager |
| 63 |
lacme is an ACME client which can be used to request X.509 certificates from |
| 64 |
ACME service providers such as Let's Encrypt or ZeroSSL. The architecture is |
| 65 |
designed with process isolation and minimal privileges in mind, and is divided |
| 66 |
into four components: |
| 67 |
. |
| 68 |
* A process to manage the account key and issue SHA-256 signatures needed for |
| 69 |
each ACME command. (This process binds to a UNIX-domain socket to reply to |
| 70 |
signature requests from the ACME client.) One can use the UNIX-domain |
| 71 |
socket forwarding facility of OpenSSH 6.7 and later to run this process on |
| 72 |
a different host. |
| 73 |
. |
| 74 |
* A "master" process, which runs as root and is the only component |
| 75 |
with access to the private key material of the server keys. It is used to |
| 76 |
fork the ACME client (and optionally the ACME webserver) after dropping |
| 77 |
root privileges. For certificate issuances, it also generates Certificate |
| 78 |
Signing Requests, then verifies the validity of the issued certificate, and |
| 79 |
optionally reloads or restarts services. |
| 80 |
. |
| 81 |
* An actual ACME client, which builds ACME commands and dialogues with |
| 82 |
the remote ACME server. Since ACME commands need to be signed with the |
| 83 |
account key, the "master" process passes the UNIX-domain socket of the |
| 84 |
account key manager to the ACME client: data signatures are requested by |
| 85 |
writing the data to be signed to the socket. |
| 86 |
. |
| 87 |
* For certificate issuances, an optional webserver, which is spawned |
| 88 |
by the "master" process when no service is listening on the HTTP port. |
| 89 |
(The only challenge type currently supported is "http-01", which requires a |
| 90 |
webserver to answer challenges.) That webserver only processes GET and |
| 91 |
HEAD requests under the "/.well-known/acme-challenge/" URI. iptables(8) |
| 92 |
rules can optionally be installed to temporarily open the HTTP port. |
| 93 |
. |
| 94 |
lacme-accountd is the first (account key manager) component. It is the only |
| 95 |
component with access to the account key. |