I think that's the same setup I mentioned above, where account reuse
only works in one direction, and therefore it fails because the v2
account isn't present on the v1 server.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We use pebble for testing: https://github.com/letsencrypt/pebble/
I'm actually not personally familiar with it though, as I haven't had
the need to set one up and modify it myself, but I understand it's
fairly straightforward to get running.
--
You received this bug notification because you are
I'd be surprised if that worked? Boulder has account reuse, but that's
for reusing an account created on v1 account with v2, not the converse.
My initial test of just putting in the old server URL doesn't seem to be
working, anyway. (Note that you have to add a server URL to the top
section of the
Ah right, it was https://github.com/mnordhoff who had one; evidence of
it working is in the PR discussion here:
https://github.com/certbot/certbot/pull/8053#issuecomment-639248307
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Robie, are you looking for a live/integration test? There's a unit test
in the linked commit. It's a little tricky to test for this, because you
either need to have an old account lying around (as new ACMEv1 accounts
can't be created anymore), or modify a boulder instance and then run
that. I
> Could you confirm which Ubuntu releases require this please? Is it all
of 16.04, 18.04 and 20.04? Is the version in Ubuntu Groovy (1.7.0-1
currently, not yet released) affected?
Yes, it is all of those, in both universe and universe updates (for
16.04 and 18.04, unless 20.04 now has universe
Public bug reported:
Let’s Encrypt is in the process of shutting down ACMEv1. The full
shutdown process will be completed in June 2021 with temporary brown-
outs starting at the beginning of the year; more specific details are
available at https://community.letsencrypt.org/t/end-of-life-plan-for-
