Your message dated Fri, 12 Aug 2016 16:01:59 +0000
with message-id <e1byeuf-0001kd...@franck.debian.org>
and subject line Bug#827357: fixed in lacme 0.1-1
has caused the Debian Bug report #827357,
regarding ITP: lacme -- ACME client written with process isolation and minimal
privileges in mind
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
827357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Guilhem Moulin <guil...@guilhem.org>
* Package name : lacme
Version : 0.1
Upstream Author : Guilhem Moulin <guil...@fripost.org>
* URL : https://git.guilhem.org/lacme/about/
* License : GPL-3+
Programming Lang: Perl
Description : 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.
--
Guilhem.
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: lacme
Source-Version: 0.1-1
We believe that the bug you reported is fixed in the latest version of
lacme, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 827...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Guilhem Moulin <guil...@guilhem.org> (supplier of updated lacme package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Tue, 08 Dec 2015 18:58:20 +0100
Source: lacme
Binary: lacme lacme-accountd
Architecture: source all
Version: 0.1-1
Distribution: unstable
Urgency: low
Maintainer: Guilhem Moulin <guil...@guilhem.org>
Changed-By: Guilhem Moulin <guil...@guilhem.org>
Description:
lacme - ACME client written with process isolation and minimal privileges
lacme-accountd - lacme account key manager
Closes: 827357 827358
Changes:
lacme (0.1-1) unstable; urgency=low
.
* Initial release. (Closes: #827357, #827358.)
Checksums-Sha1:
fbf12143a081bb347bcf9e605b03173c378f30a6 1808 lacme_0.1-1.dsc
eb1cbf434e94bdd25b177f6e853d457a5c4f718f 39226 lacme_0.1.orig.tar.gz
96a11dbed7d99c39c12668d79b78b81ebfdff9fc 2896 lacme_0.1-1.debian.tar.xz
98441617da6cdeca3e3900efcf91c2114afdb4e9 8040 lacme-accountd_0.1-1_all.deb
d5330c92040398070dff015de406553da2c6f764 23864 lacme_0.1-1_all.deb
Checksums-Sha256:
c403c22ceb3bc5727ef7f68d24197266a5b8b425ffaad5264cd74bcf98bf0bf0 1808
lacme_0.1-1.dsc
963697c29270ed2e01147677bf1c033a104ea5da4631330490ea996240c40d01 39226
lacme_0.1.orig.tar.gz
12f22f0fd42d0611d164b90fd9710dbdf539f24da22e3029c982738e0bd7f17e 2896
lacme_0.1-1.debian.tar.xz
2caf10dd9b6a78978dea42e79870c715f7f9e8294124779fda8654cbdef238a8 8040
lacme-accountd_0.1-1_all.deb
46c42310130aa2f7a7279127924f6fce0de7289c8c7880fc7a7c4e47a63ab49b 23864
lacme_0.1-1_all.deb
Files:
93a08cdfd802d435ab89098162ef2d2a 1808 utils optional lacme_0.1-1.dsc
18db83d9d6a2fa1fe628555f6c7bdc2b 39226 utils optional lacme_0.1.orig.tar.gz
8031723b842b9ae5cff6052a594f1531 2896 utils optional lacme_0.1-1.debian.tar.xz
a163ba23c1e11a8bc761c5eebd3325b4 8040 utils optional
lacme-accountd_0.1-1_all.deb
b516a985e054a84ef24aa5b5da9a4cf5 23864 utils optional lacme_0.1-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJXm6D0AAoJEPNPCXROn13ZUZUP+gP4i6czYypM0EiENsEApywQ
25nhZ00qx2w67GhBqeiQ4A5ITT60/F7ONf2sPxp9yblrN1Z215JTwtpgiRmzuJX4
3AJVyxAVDwPtDLrht9kBv3VDlBt65KbjllXO/GtjqEf/0xJrA5iMdV6nm9cROavs
YcU57rZc2NVbGO75AqObZZrjKNmRK3sMbuDf6eWDCnU/QEl6HTc2WtHAhv46kKk+
s8C0iz3zQG0TKdGDbyH7AqgxHuvk1w+ycE+YA9mYJhpfhNQewcMFB7SJbsXZc5Bi
OQfrNDfsGZui1wai+fjW4c1eNnPf0NjKzwrBnsfGHskCUVqRxXUY2yKXMQ2M4C/b
Ilkqz1d00fa0dDm81YgbMilGg0mMWyp3AfzhhqWa8wuOr5rcHaYlTWFgtf1GiLZ9
MVW9FtSGYCWRrTWX+6wlt26O+MZgieYJhksdMzAczV1lGMhdo3qU17yf3458ynp/
8i4eTC++fogYm6ucXv0noH4gH7zSZj9vk268r4u5tHtdLRvJ702gyO2Q83C1g5e3
LymKz8Kq6E+NMLpHXfWRaWEMJ75Y2IfurKwZZ7w051+mbu+3tumMjtXbOGhY0+iv
7RJRY3aOCLAlvsot4GpMMWKCBQQTTLsVQZUg44IiBSZCOUsqNutgoFNJUTpLaFnc
9PTtjZoJDhIqbmlMJy1b
=P00C
-----END PGP SIGNATURE-----
--- End Message ---
