lacme 0.4-1 source package in Ubuntu

Changelog

lacme (0.4-1) unstable; urgency=medium

  * Fix manpage generation with pandoc >=1.18.  (Closes: #869885.)

 -- Guilhem Moulin <email address hidden>  Fri, 28 Jul 2017 00:24:06 +0200

Upload details

Uploaded by:
Guilhem Moulin on 2017-07-28
Uploaded to:
Sid
Original maintainer:
Guilhem Moulin
Architectures:
all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Bionic release on 2017-10-24 universe misc
Artful release on 2017-07-28 universe misc

Builds

Artful: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
lacme_0.4-1.dsc 1.8 KiB 4048aa0bb33d7a26e07268245e01a80c9c06c055038d95a8a5346489c9bf8ae9
lacme_0.4.orig.tar.gz 44.2 KiB 8dfed70da83702a09805ed8ca79d394709660b9961de763d415ea5e81f859958
lacme_0.4-1.debian.tar.xz 3.1 KiB 634cd8abdc4cd543928a44266696bb17a16a58c921bc3340c1f5b4b8bf42e916

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: 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.