<feed xmlns='http://www.w3.org/2005/Atom'>
<title>lacme/debian/patches/series, branch debian/bullseye</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>Backport upstream patches to fix fix post-issuance validation logic.</title>
<updated>2024-06-13T17:18:49+00:00</updated>
<author>
<name>Guilhem Moulin</name>
<email>guilhem@debian.org</email>
</author>
<published>2024-06-13T16:43:06+00:00</published>
<link rel='alternate' type='text/html' href='http://git.guilhem.org/lacme/commit/?id=edb498097d7fd4d52c4f49c164776f7b15e59703'/>
<id>edb498097d7fd4d52c4f49c164776f7b15e59703</id>
<content type='text'>
As well as the upstream test suite.

Closes: #1072847
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
As well as the upstream test suite.

Closes: #1072847
</pre>
</div>
</content>
</entry>
<entry>
<title>client: Handle "ready" → "processing" → "valid" status change during newOrder.</title>
<updated>2023-04-28T08:06:27+00:00</updated>
<author>
<name>Guilhem Moulin</name>
<email>guilhem@debian.org</email>
</author>
<published>2023-04-28T08:06:27+00:00</published>
<link rel='alternate' type='text/html' href='http://git.guilhem.org/lacme/commit/?id=fc4fae45811dd87a8e34e31ca2a06fc0b5cc6909'/>
<id>fc4fae45811dd87a8e34e31ca2a06fc0b5cc6909</id>
<content type='text'>
Instead of just "ready" → "valid", which may be what we observe when the
server is fast enough, but according to RFC 8555 sec. 7.1.6 the state
actually transitions via "processing" state and we need to account for
that.

It appears Let's Encrypt staging environment now has different timing
conditions and lacme is unable to request certificates due to this
issue.

Cherry-picked from 53238c70f7a12e233a6ca83cf2b50168e5b9592e.

Closes: #1034834
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Instead of just "ready" → "valid", which may be what we observe when the
server is fast enough, but according to RFC 8555 sec. 7.1.6 the state
actually transitions via "processing" state and we need to account for
that.

It appears Let's Encrypt staging environment now has different timing
conditions and lacme is unable to request certificates due to this
issue.

Cherry-picked from 53238c70f7a12e233a6ca83cf2b50168e5b9592e.

Closes: #1034834
</pre>
</div>
</content>
</entry>
<entry>
<title>Refresh patches.</title>
<updated>2020-08-03T23:40:59+00:00</updated>
<author>
<name>Guilhem Moulin</name>
<email>guilhem@fripost.org</email>
</author>
<published>2020-08-03T22:52:29+00:00</published>
<link rel='alternate' type='text/html' href='http://git.guilhem.org/lacme/commit/?id=35e8d56f2c42d789e6273c757b6a835c3416a2f8'/>
<id>35e8d56f2c42d789e6273c757b6a835c3416a2f8</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Mention the Debian BTS in the manpages.</title>
<updated>2016-06-14T15:45:58+00:00</updated>
<author>
<name>Guilhem Moulin</name>
<email>guilhem@fripost.org</email>
</author>
<published>2016-06-14T15:39:16+00:00</published>
<link rel='alternate' type='text/html' href='http://git.guilhem.org/lacme/commit/?id=955a29db14877a8374d7ef334e33a042925df418'/>
<id>955a29db14877a8374d7ef334e33a042925df418</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
