aboutsummaryrefslogtreecommitdiffstats
path: root/debian/lacme.NEWS
diff options
context:
space:
mode:
authorGuilhem Moulin <guilhem@debian.org>2023-04-28 10:06:27 +0200
committerGuilhem Moulin <guilhem@debian.org>2023-04-28 10:06:27 +0200
commitfc4fae45811dd87a8e34e31ca2a06fc0b5cc6909 (patch)
tree7a05c8fe8c587fddeb3674ac39d910d0393c557d /debian/lacme.NEWS
parent6c1325a2b2e5c6518e99f2bc60a939c28c88e41c (diff)
client: Handle "ready" → "processing" → "valid" status change during newOrder.
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
Diffstat (limited to 'debian/lacme.NEWS')
0 files changed, 0 insertions, 0 deletions