<feed xmlns='http://www.w3.org/2005/Atom'>
<title>lacme/lacme, branch master</title>
<subtitle>Small ACME client written with process isolation and minimal privileges in mind</subtitle>
<link rel='alternate' type='text/html' href='http://git.guilhem.org/lacme/'/>
<entry>
<title>Prepare new release v0.8.3.</title>
<updated>2024-06-13T15:39:34+00:00</updated>
<author>
<name>Guilhem Moulin</name>
<email>guilhem@fripost.org</email>
</author>
<published>2024-06-13T15:39:34+00:00</published>
<link rel='alternate' type='text/html' href='http://git.guilhem.org/lacme/commit/?id=ce6a95d172dbefd0e310c46e0a0d9c56d19e34ca'/>
<id>ce6a95d172dbefd0e310c46e0a0d9c56d19e34ca</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix post-issuance validation logic.</title>
<updated>2024-06-13T14:48:05+00:00</updated>
<author>
<name>Guilhem Moulin</name>
<email>guilhem@fripost.org</email>
</author>
<published>2024-06-13T01:32:04+00:00</published>
<link rel='alternate' type='text/html' href='http://git.guilhem.org/lacme/commit/?id=9cb882a468843bf8ce9598de8769d5baaaaae3ea'/>
<id>9cb882a468843bf8ce9598de8769d5baaaaae3ea</id>
<content type='text'>
Rather than adding intermediates in the certificate bundle we now
validate the leaf certificate with intermediates as untrusted (used for
chain building only).  Only the root certificates are used as trust
anchor.

Not pining intermediate certificates anymore is in line with Let's
Encrypt's latest recommendations:

    Rotating the set of intermediates we issue from helps keep the
    Internet agile and more secure.  It encourages automation and
    efficiency, and discourages outdated practices like key pinning.
    “Key Pinning” is a practice in which clients — either ACME clients
    getting certificates for their site, or apps connecting to their own
    backend servers — decide to trust only a single issuing intermediate
    certificate rather than delegating trust to the system trust store.
    Updating pinned keys is a manual process, which leads to an
    increased risk of errors and potential business continuity failures.
    — https://letsencrypt.org/2024/03/19/new-intermediate-certificates:
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Rather than adding intermediates in the certificate bundle we now
validate the leaf certificate with intermediates as untrusted (used for
chain building only).  Only the root certificates are used as trust
anchor.

Not pining intermediate certificates anymore is in line with Let's
Encrypt's latest recommendations:

    Rotating the set of intermediates we issue from helps keep the
    Internet agile and more secure.  It encourages automation and
    efficiency, and discourages outdated practices like key pinning.
    “Key Pinning” is a practice in which clients — either ACME clients
    getting certificates for their site, or apps connecting to their own
    backend servers — decide to trust only a single issuing intermediate
    certificate rather than delegating trust to the system trust store.
    Updating pinned keys is a manual process, which leads to an
    increased risk of errors and potential business continuity failures.
    — https://letsencrypt.org/2024/03/19/new-intermediate-certificates:
</pre>
</div>
</content>
</entry>
<entry>
<title>Pass `-in /dev/stdin` option to openssl(1) to avoid warning with recent versions.</title>
<updated>2024-06-13T13:41:12+00:00</updated>
<author>
<name>Guilhem Moulin</name>
<email>guilhem@fripost.org</email>
</author>
<published>2024-06-13T01:33:20+00:00</published>
<link rel='alternate' type='text/html' href='http://git.guilhem.org/lacme/commit/?id=bf4d2d13ffcd894c6e7765dbd366f1163c69c9e1'/>
<id>bf4d2d13ffcd894c6e7765dbd366f1163c69c9e1</id>
<content type='text'>
OpenSSL 3.2 from Debian sid spews

    Warning: Reading certificate from stdin since no -in or -new option is given

without an explicit `-in /dev/stdin`.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
OpenSSL 3.2 from Debian sid spews

    Warning: Reading certificate from stdin since no -in or -new option is given

without an explicit `-in /dev/stdin`.
</pre>
</div>
</content>
</entry>
<entry>
<title>Prepare new release v0.8.2.</title>
<updated>2023-04-25T18:06:22+00:00</updated>
<author>
<name>Guilhem Moulin</name>
<email>guilhem@fripost.org</email>
</author>
<published>2023-04-25T18:06:22+00:00</published>
<link rel='alternate' type='text/html' href='http://git.guilhem.org/lacme/commit/?id=c80a2530eb014b34a314e078fec2589bc7969e33'/>
<id>c80a2530eb014b34a314e078fec2589bc7969e33</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Prepare new release v0.8.1.</title>
<updated>2023-01-25T02:23:51+00:00</updated>
<author>
<name>Guilhem Moulin</name>
<email>guilhem@fripost.org</email>
</author>
<published>2023-01-25T02:23:51+00:00</published>
<link rel='alternate' type='text/html' href='http://git.guilhem.org/lacme/commit/?id=b3af3526b293f396da02a6276ea86ca17dcd2d03'/>
<id>b3af3526b293f396da02a6276ea86ca17dcd2d03</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>lacme: pass a temporary JSON file with the client configuration to the internal client.</title>
<updated>2021-02-25T09:30:22+00:00</updated>
<author>
<name>Guilhem Moulin</name>
<email>guilhem@fripost.org</email>
</author>
<published>2021-02-25T00:41:59+00:00</published>
<link rel='alternate' type='text/html' href='http://git.guilhem.org/lacme/commit/?id=9a8f705eddd18ccc9a24fe0e7efe6b5a87b2be09'/>
<id>9a8f705eddd18ccc9a24fe0e7efe6b5a87b2be09</id>
<content type='text'>
So it doesn't have to parse the INI file again.  Also, while lacme.conf
is world-readable by default, one might restrict permissions and add
private information in there, not realizing that everything, including
comments, will be readable by the client.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
So it doesn't have to parse the INI file again.  Also, while lacme.conf
is world-readable by default, one might restrict permissions and add
private information in there, not realizing that everything, including
comments, will be readable by the client.
</pre>
</div>
</content>
</entry>
<entry>
<title>lacme: split certificates using Net::SSLeay::PEM_* instead of calling openssl.</title>
<updated>2021-02-24T23:37:17+00:00</updated>
<author>
<name>Guilhem Moulin</name>
<email>guilhem@fripost.org</email>
</author>
<published>2021-02-24T23:30:37+00:00</published>
<link rel='alternate' type='text/html' href='http://git.guilhem.org/lacme/commit/?id=f09c95ea97c9bdee92f7c7622689aed540373a73'/>
<id>f09c95ea97c9bdee92f7c7622689aed540373a73</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>lacme: improve install_cert()'s handling of temporary files.</title>
<updated>2021-02-24T20:56:10+00:00</updated>
<author>
<name>Guilhem Moulin</name>
<email>guilhem@fripost.org</email>
</author>
<published>2021-02-24T20:50:11+00:00</published>
<link rel='alternate' type='text/html' href='http://git.guilhem.org/lacme/commit/?id=491998131f18d136ca37f15898d07062ad7a1fae'/>
<id>491998131f18d136ca37f15898d07062ad7a1fae</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>lacme: Return an error when the 'mode'/'chown' isn't a number.</title>
<updated>2021-02-24T20:32:06+00:00</updated>
<author>
<name>Guilhem Moulin</name>
<email>guilhem@fripost.org</email>
</author>
<published>2021-02-24T20:28:31+00:00</published>
<link rel='alternate' type='text/html' href='http://git.guilhem.org/lacme/commit/?id=ea5a51ecaa72c8277b4f878cf3635025d757fa37'/>
<id>ea5a51ecaa72c8277b4f878cf3635025d757fa37</id>
<content type='text'>
oct("foobar") is 0, definitely not what we want.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
oct("foobar") is 0, definitely not what we want.
</pre>
</div>
</content>
</entry>
<entry>
<title>lacme: Add 'owner' resp. 'mode' as (prefered) alias for 'chown' resp. 'chmod'.</title>
<updated>2021-02-24T20:32:06+00:00</updated>
<author>
<name>Guilhem Moulin</name>
<email>guilhem@fripost.org</email>
</author>
<published>2021-02-24T20:24:13+00:00</published>
<link rel='alternate' type='text/html' href='http://git.guilhem.org/lacme/commit/?id=c6a4aaa6128d55ba5f7f3cd2bd75f789f69ae407'/>
<id>c6a4aaa6128d55ba5f7f3cd2bd75f789f69ae407</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
