lacme, branch debian/bookworm Small ACME client written with process isolation and minimal privileges in mind http://git.guilhem.org/lacme/atom?h=debian%2Fbookworm 2024-06-15T22:10:26Z Typofix 2024-06-15T22:10:26Z Guilhem Moulin guilhem@debian.org 2024-06-15T19:24:54Z urn:sha1:c750e5b8a31ed5267150167ac68b5a5f89fc488b Pointed by Jonathan Wiltshire at https://bugs.debian.org/1073174#12 . Thanks! Salsa CI: Set RELEASE=bookworm and disable Lintian job. 2024-06-15T22:10:19Z Guilhem Moulin guilhem@debian.org 2024-06-13T17:48:50Z urn:sha1:db39468162d7631abe75bd2cfbde92c69a3520cd Gbp-Dch: Ignore Update changelog for 0.8.2-1+deb12u1 release 2024-06-13T23:45:16Z Guilhem Moulin guilhem@debian.org 2024-06-13T23:21:05Z urn:sha1:c67e0904613dc0e5f1937a511be4198274d8111d d/gbp.conf: Set 'debian-branch = debian/bookworm'. 2024-06-13T23:45:16Z Guilhem Moulin guilhem@debian.org 2024-06-13T23:15:11Z urn:sha1:80e4e3f08ac66871fd953ab4806e1be6f5f130b0 Backport upstream patches to fix fix post-issuance validation logic. 2024-06-13T23:45:12Z Guilhem Moulin guilhem@debian.org 2024-06-13T23:14:22Z urn:sha1:4340c68fa9626ab3db81dd774f79305dc774a7e6 As well as the upstream test suite. Closes: #1072847 Update changelog for 0.8.2-1 release 2023-04-25T18:21:40Z Guilhem Moulin guilhem@debian.org 2023-04-25T18:09:16Z urn:sha1:d531c00ae1c422b3f0948d297098722fb448edb5 Merge tag 'v0.8.2' into debian/latest 2023-04-25T18:07:41Z Guilhem Moulin guilhem@debian.org 2023-04-25T18:07:41Z urn:sha1:5d965c73acc3c3e53a407186910cf6a7b8ccd812 Release version 0.8.2 Prepare new release v0.8.2. 2023-04-25T18:06:22Z Guilhem Moulin guilhem@fripost.org 2023-04-25T18:06:22Z urn:sha1:c80a2530eb014b34a314e078fec2589bc7969e33 tests: Point stretch's archive URL to archive.d.o. 2023-04-25T09:59:39Z Guilhem Moulin guilhem@fripost.org 2023-04-25T09:59:39Z urn:sha1:5d9d1ce570c0fa613e1dc2345047a0ff95f781c5 See https://lists.debian.org/msgid-search/87tty79lwo.fsf@43-1.org . client: Handle "ready" → "processing" → "valid" status change during newOrder. 2023-04-25T09:11:03Z Guilhem Moulin guilhem@fripost.org 2023-04-25T08:51:36Z urn:sha1:53238c70f7a12e233a6ca83cf2b50168e5b9592e 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. Thanks to Alexander Borkowski for the report!