From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] dehydrated: critical bump to 0.6.5
Date: Mon, 02 Sep 2019 17:24:42 +0200 [thread overview]
Message-ID: <87blw23emd.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190819163749.14021-1-arnout@mind.be> (Arnout Vandecappelle's message of "Mon, 19 Aug 2019 18:37:49 +0200")
>>>>> "Arnout" == Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> writes:
> On July 3, 2019, Let's Encrypt deployed new ACME server software that no
> longer returns the 'id' field in the account information JSON.
> Dehydrated relied on this field, even though it is not specified by RFC
> 8555. Because of this, dehydrated can no longer create a new account on
> Let's Encrypt.
> This was fixed by upstream commits be13dcd and 4f358e2. But the latter
> broke ACMEv1 support so was fixed again in commit f60f2f8.
> Cherry-picking this correctly is tricky, so instead just bump the
> version. There are quite a few non-bugfix changes that are included this
> way, but it's more risky to try to cherry-pick.
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> Since this issue essentially breaks dehydrated for new accounts (i.e.
> any new deployment), I think it's for master and it should be backported
> to 2019.02.x
Committed to 2019.02.x and 2019.05.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2019-09-02 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 16:37 [Buildroot] [PATCH] dehydrated: critical bump to 0.6.5 Arnout Vandecappelle
2019-08-19 17:09 ` Peter Korsgaard
2019-08-19 19:47 ` Thomas Petazzoni
2019-09-02 15:24 ` Peter Korsgaard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blw23emd.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox