How to Install and Uninstall lacme Package on Ubuntu 21.10 (Impish Indri)
Last updated: November 07,2024
1. Install "lacme" package
Learn how to install lacme on Ubuntu 21.10 (Impish Indri)
$
sudo apt update
Copied
$
sudo apt install
lacme
Copied
2. Uninstall "lacme" package
Here is a brief guide to show you how to uninstall lacme on Ubuntu 21.10 (Impish Indri):
$
sudo apt remove
lacme
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the lacme package on Ubuntu 21.10 (Impish Indri)
Package: lacme
Architecture: all
Version: 0.8.0-2
Priority: optional
Section: universe/utils
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Guilhem Moulin
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 136
Depends: adduser, libconfig-tiny-perl, libjson-perl, libnet-ssleay-perl, libtimedate-perl, libwww-perl, openssl (>= 1.1.0~), perl:any
Recommends: lacme-accountd (>= 0.8.0), liblwp-protocol-https-perl
Filename: pool/universe/l/lacme/lacme_0.8.0-2_all.deb
Size: 42192
MD5sum: 2c0c767c910f08eb55f78fd25f67cb6d
SHA1: ae2a19b4df0abed9712eee84a7f93f5b02c034dc
SHA256: 7e28133a8e3687586f0effd7912a5ee66f2ce19682b32c731499111f2c3b9b87
SHA512: 9bfd03b28581237b8768ed87dcefcc3abd444c4376ce227ca1a326898cf6ae0d6136ffcdab542bb68e70bc8438d5bedf0511e38772c8a2c55ae00032c193a0e8
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.8.0-2
Priority: optional
Section: universe/utils
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Guilhem Moulin
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 136
Depends: adduser, libconfig-tiny-perl, libjson-perl, libnet-ssleay-perl, libtimedate-perl, libwww-perl, openssl (>= 1.1.0~), perl:any
Recommends: lacme-accountd (>= 0.8.0), liblwp-protocol-https-perl
Filename: pool/universe/l/lacme/lacme_0.8.0-2_all.deb
Size: 42192
MD5sum: 2c0c767c910f08eb55f78fd25f67cb6d
SHA1: ae2a19b4df0abed9712eee84a7f93f5b02c034dc
SHA256: 7e28133a8e3687586f0effd7912a5ee66f2ce19682b32c731499111f2c3b9b87
SHA512: 9bfd03b28581237b8768ed87dcefcc3abd444c4376ce227ca1a326898cf6ae0d6136ffcdab542bb68e70bc8438d5bedf0511e38772c8a2c55ae00032c193a0e8
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