| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| Mention-the-Debian-BTS-in-the-manpages.patch | Mention the Debian BTS in the manpages. | Guilhem Moulin <guilhem@debian.org> | not-needed | 2016-12-01 | ||
| client-Handle-ready-processing-valid-status-change-during.patch | =?utf-8?q?client=3A_Handle_=22ready=22_=E2=86=92_=22processing=22_?= =?utf-8?q?=E2=86=92_=22valid=22_status_change_during_newOrder=2E?= 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! |
Guilhem Moulin <guilhem@fripost.org> | no | debian | 2023-04-25 |