How to Install and Uninstall lacme Package on Ubuntu 20.10 (Groovy Gorilla)
Last updated: November 25,2024
1. Install "lacme" package
Here is a brief guide to show you how to install lacme on Ubuntu 20.10 (Groovy Gorilla)
$
sudo apt update
Copied
$
sudo apt install
lacme
Copied
2. Uninstall "lacme" package
This tutorial shows how to uninstall lacme on Ubuntu 20.10 (Groovy Gorilla):
$
sudo apt remove
lacme
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the lacme package on Ubuntu 20.10 (Groovy Gorilla)
Package: lacme
Architecture: all
Version: 0.6.1-1
Priority: optional
Section: universe/utils
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Guilhem Moulin
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 97
Depends: libconfig-tiny-perl, libjson-perl, libnet-ssleay-perl, libtimedate-perl, libtypes-serialiser-perl, libwww-perl, openssl, perl:any
Recommends: lacme-accountd (= 0.6.1-1), liblwp-protocol-https-perl
Filename: pool/universe/l/lacme/lacme_0.6.1-1_all.deb
Size: 27836
MD5sum: b3ae230dd61eb0f84c24ddfb6ba6d03a
SHA1: 248100fea31177339e1d6299240378605afabbff
SHA256: 7317dd1b9a2203e4a43c1518ab5bb9806e3389bcb2b1a7200d77554fec06881a
SHA512: 4a8e385f2c34baa98448dc6327655cb7d3d1f98e8a3d21192cd6f3180cbf89fa42e583a26b8d76d4b9002de3ea27528cf0a6a839a1de9922e32209e991d0256a
Homepage: https://git.guilhem.org/lacme/about/
Description-en: 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.
Description-md5: 17b092dc67a598023e7db924caa2c8a3
Architecture: all
Version: 0.6.1-1
Priority: optional
Section: universe/utils
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Guilhem Moulin
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 97
Depends: libconfig-tiny-perl, libjson-perl, libnet-ssleay-perl, libtimedate-perl, libtypes-serialiser-perl, libwww-perl, openssl, perl:any
Recommends: lacme-accountd (= 0.6.1-1), liblwp-protocol-https-perl
Filename: pool/universe/l/lacme/lacme_0.6.1-1_all.deb
Size: 27836
MD5sum: b3ae230dd61eb0f84c24ddfb6ba6d03a
SHA1: 248100fea31177339e1d6299240378605afabbff
SHA256: 7317dd1b9a2203e4a43c1518ab5bb9806e3389bcb2b1a7200d77554fec06881a
SHA512: 4a8e385f2c34baa98448dc6327655cb7d3d1f98e8a3d21192cd6f3180cbf89fa42e583a26b8d76d4b9002de3ea27528cf0a6a839a1de9922e32209e991d0256a
Homepage: https://git.guilhem.org/lacme/about/
Description-en: 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.
Description-md5: 17b092dc67a598023e7db924caa2c8a3