lacme 0.8.0-2 source package in Ubuntu

Changelog

lacme (0.8.0-2) unstable; urgency=medium

  * d/lacme.postrm: Don't delete system users on purge.  There might be files
    on disk owned by _lacme-client when 'challenge-directory' is set in the
    configuration (closes: #988032).

 -- Guilhem Moulin <email address hidden>  Tue, 04 May 2021 01:37:13 +0200

Upload details

Uploaded by:
Guilhem Moulin
Uploaded to:
Sid
Original maintainer:
Guilhem Moulin
Architectures:
all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Jammy release universe misc

Builds

Impish: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
lacme_0.8.0-2.dsc 1.8 KiB 482c9aa2c63aac6e9fa7efb4d5dac8d3aed4df9ae1e29aaaa7d3ec86d475dc00
lacme_0.8.0.orig.tar.gz 79.4 KiB 9612497a6808d1d9780a6028241e233e78eb10f1ff1efe53f81f6c860708ecd0
lacme_0.8.0-2.debian.tar.xz 15.3 KiB 6a6a3b10cb401b28cee67208dae386fa3eab674b0f15200a7ad15c3a2d174f5b

Available diffs

No changes file available.

Binary packages built by this source

lacme: ACME client written with process isolation and minimal privileges in mind

 lacme 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: No summary available for lacme-accountd in ubuntu kinetic.

No description available for lacme-accountd in ubuntu kinetic.