lacme, branch debian/bullseye Small ACME client written with process isolation and minimal privileges in mind Typofix 2024-06-15T19:27:41+00:00 Guilhem Moulin guilhem@debian.org 2024-06-15T19:24:54+00:00 6362716a94ef687e2d1f5bf662a3329866346675 Pointed by Jonathan Wiltshire at https://bugs.debian.org/1073174#12 . Thanks! 
Pointed by Jonathan Wiltshire at https://bugs.debian.org/1073174#12 .
Thanks!
Salsa CI: Set RELEASE=bullseye and disable Lintian job. 2024-06-13T17:48:50+00:00 Guilhem Moulin guilhem@debian.org 2024-06-13T17:48:50+00:00 6a6146c9f860c9efa8729931c6e439b71b81039e Gbp-Dch: Ignore 
Gbp-Dch: Ignore
Update changelog for 0.8.0-2+deb11u2 release 2024-06-13T17:20:05+00:00 Guilhem Moulin guilhem@debian.org 2024-06-13T17:20:05+00:00 f6bfd9b91629bd498301b34de8ea2b28d33ceb7d 






Backport upstream patches to fix fix post-issuance validation logic.
2024-06-13T17:18:49+00:00

Guilhem Moulin
guilhem@debian.org

2024-06-13T16:43:06+00:00

edb498097d7fd4d52c4f49c164776f7b15e59703

As well as the upstream test suite.

Closes: #1072847





As well as the upstream test suite.

Closes: #1072847







Update changelog for 0.8.0-2+deb12u1 release
2023-04-28T08:46:20+00:00

Guilhem Moulin
guilhem@debian.org

2023-04-28T08:26:28+00:00

3307551410bb24d41fa947701e7b3a031f29fb69












d/gbp.conf: Set 'debian-branch = debian/bullseye'.
2023-04-28T08:25:43+00:00

Guilhem Moulin
guilhem@debian.org

2023-04-28T08:25:43+00:00

f2f3c1a04e31568dcb021c98cb8d6eceae96bea5












client: Handle "ready" → "processing" → "valid" status change during newOrder.
2023-04-28T08:06:27+00:00

Guilhem Moulin
guilhem@debian.org

2023-04-28T08:06:27+00:00

fc4fae45811dd87a8e34e31ca2a06fc0b5cc6909

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





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







Prepare new release.
2021-05-03T23:37:14+00:00

Guilhem Moulin
guilhem@debian.org

2021-05-03T23:37:14+00:00

6c1325a2b2e5c6518e99f2bc60a939c28c88e41c












d/lacme.postrm: Don't delete system users on purge.
2021-02-22T19:37:57+00:00

Guilhem Moulin
guilhem@debian.org

2021-02-22T19:37:57+00:00

3d1bc4f299d693b3b3d2bc77387f866bbfc14dd9

_lacme-www shouldn't own any file or directories, but there might be
files on disk owned by _lacme-client when 'challenge-directory' is used.

See https://wiki.debian.org/AccountHandlingInMaintainerScripts#Reasons_for_not_deleting_accounts .





_lacme-www shouldn't own any file or directories, but there might be
files on disk owned by _lacme-client when 'challenge-directory' is used.

See https://wiki.debian.org/AccountHandlingInMaintainerScripts#Reasons_for_not_deleting_accounts .







Prepare new release.
2021-02-22T02:32:01+00:00

Guilhem Moulin
guilhem@debian.org

2021-02-22T02:32:01+00:00

ae52bdc9a590a28d89a69cab783973fcffa5cb7f