diff options
| -rw-r--r-- | Changelog | 11 | ||||
| -rwxr-xr-x | client | 2 | ||||
| -rwxr-xr-x | lacme | 2 | ||||
| -rwxr-xr-x | lacme-accountd | 2 | 
4 files changed, 14 insertions, 3 deletions
@@ -1,3 +1,14 @@ +lacme (0.8.2) upstream; + +  + client: 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. +  - Test suite: Point stretch's archive URL to archive.d.o. + + -- Guilhem Moulin <guilhem@fripost.org>  Tue, 25 Apr 2023 20:06:22 +0200 +  lacme (0.8.1) upstream;   + lacme-accountd: improve log messages and refactor logging logic. @@ -43,7 +43,7 @@ use warnings;  # instance own by another user and created with umask 0177) is not a  # problem since SOCKET_FD can be bound as root prior to the execve(2). -our $VERSION = '0.8.1'; +our $VERSION = '0.8.2';  my $PROTOCOL_VERSION = 1;  my $NAME = 'lacme-client'; @@ -22,7 +22,7 @@ use v5.14.2;  use strict;  use warnings; -our $VERSION = '0.8.1'; +our $VERSION = '0.8.2';  my $NAME = 'lacme';  use Errno 'EINTR'; diff --git a/lacme-accountd b/lacme-accountd index a9f5469..8d2c599 100755 --- a/lacme-accountd +++ b/lacme-accountd @@ -23,7 +23,7 @@ use v5.14.2;  use strict;  use warnings; -our $VERSION = '0.8.1'; +our $VERSION = '0.8.2';  my $PROTOCOL_VERSION = 1;  my $NAME = 'lacme-accountd';  | 
