Package: lacme Version: 0.8.1-1 Severity: important Control: found -1 0.8.0-2
The lacme client fails to handle "ready" → "processing" → "valid" status change during newOrder, instead of just "ready" → "valid". The latter 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. As of today `lacme newOrder` still works on the production Let's Encrypt ACME server, but now fails on the staging one. It's unclear whether the staging environment has different timing conditions, or if there were changes in the boulder codebase which will break lacme once pushed to production. -- Guilhem.
signature.asc
Description: PGP signature
