diff options
Diffstat (limited to 'debian/control')
| -rw-r--r-- | debian/control | 54 |
1 files changed, 50 insertions, 4 deletions
diff --git a/debian/control b/debian/control index 533ea03..258ee91 100644 --- a/debian/control +++ b/debian/control @@ -4,16 +4,22 @@ Priority: optional Maintainer: Guilhem Moulin <guilhem@guilhem.org> Build-Depends: debhelper (>= 9), jq, pandoc Standards-Version: 3.9.6 +Homepage: https://git.guilhem.org/lacme/about/ Vcs-Git: https://git.guilhem.org/lacme Vcs-Browser: https://git.guilhem.org/lacme Package: lacme Architecture: all Depends: ${misc:Depends}, ${perl:Depends}, - libwww-perl, libjson-perl, libconfig-tiny-perl, - libnet-ssleay-perl, openssl -Recommends: liblwp-protocol-https-perl, - libcrypt-openssl-bignum-perl, libcrypt-openssl-rsa-perl + openssl, + libconfig-tiny-perl, + libjson-perl, + libwww-perl, + libnet-ssleay-perl +Recommends: + liblwp-protocol-https-perl +Suggests: + lacme-accountd (= ${binary:Version}) Description: ACME client written with process isolation and minimal privileges in mind lacme is divided into four components, each with its own executable: . @@ -43,3 +49,43 @@ Description: ACME client written with process isolation and minimal privileges i HEAD requests under the "/.well-known/acme-challenge/" URI. By default some iptables(8) rules are automatically installed to open the HTTP port, and removed afterwards. + +Package: lacme-accountd +Architecture: all +Depends: ${misc:Depends}, ${perl:Depends}, + libconfig-tiny-perl, + libjson-perl +Recommends: libcrypt-openssl-rsa-perl +Description: lacme account key manager + lacme is an ACME client written with process isolation and minimal privileges + in mind. It is divided into four components, each with its own executable: + . + * A process to manage the account key and issue SHA-256 signatures needed for + each ACME command. (This process binds to a UNIX-domain socket to reply to + signature requests from the ACME client.) One can use the UNIX-domain + socket forwarding facility of OpenSSH 6.7 and later to run this process on + a different host. + . + * A "master" process, which runs as root and is the only component + with access to the private key material of the server keys. It is used to + fork the ACME client (and optionally the ACME webserver) after dropping + root privileges. For certificate issuances, it also generates Certificate + Signing Requests, then verifies the validity of the issued certificate, and + optionally reloads or restarts services. + . + * An actual ACME client, which builds ACME commands and dialogues with + the remote ACME server. Since ACME commands need to be signed with the + account key, the "master" process passes the UNIX-domain socket of the + account key manager to the ACME client: data signatures are requested by + writing the data to be signed to the socket. + . + * For certificate issuances, an optional webserver, which is spawned + by the "master" process when no service is listening on the HTTP port. + (The only challenge type currently supported is "http-01", which requires a + webserver to answer challenges.) That webserver only processes GET and + HEAD requests under the "/.well-known/acme-challenge/" URI. By default + some iptables(8) rules are automatically installed to open the HTTP port, + and removed afterwards. + . + lacme-accountd is the first (account key manager) component. It is the only + component with access to the account key. |