Skip to contentSkip to conversation

dehydrated: critical bump to 0.6.5

PATCH New Arnout Vandecappelle (Essensium/Mind) 3 participants 4 messages Aug 19, 2019 – Sep 2, 2019

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 dehydrated: critical bump to 0.6.5

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.

---
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

---
 package/dehydrated/dehydrated.hash | 4 ++--
 package/dehydrated/dehydrated.mk   | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)
package/dehydrated/dehydrated.hash +2 -2
index 1d194e5a7d..388dd24749 100644
@@ -1,6 +1,6 @@
 # Locally computed after verifying
-# https://github.com/lukas2511/dehydrated/releases/download/v0.6.2/dehydrated-0.6.2.tar.gz.asc
+# https://github.com/lukas2511/dehydrated/releases/download/v0.6.5/dehydrated-0.6.5.tar.gz.asc
 # with key 3C2F2605E078A1E18F4793909C4DBE6CF438F333 from https://keybase.io/lukas2511
-sha256  163384479199f06f59382ceb6291a299567a2f4f0b963b9b61f2db65a407e80e  dehydrated-0.6.2.tar.gz
+sha256  10aabd0027450bc70a18e49acaca7a9697e0cfb92368d3e508b7a4d6d69bfa35 dehydrated-0.6.5.tar.gz
 # License, locally computed
 sha256  b4583b7dd07e3e2a08906de38e7e329d41f921ed9dcb6310b3886e013a6b8723  LICENSE
package/dehydrated/dehydrated.mk +1 -1
index b7de27a407..17c67b8478 100644
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-DEHYDRATED_VERSION = 0.6.2
+DEHYDRATED_VERSION = 0.6.5
 DEHYDRATED_SITE = https://github.com/lukas2511/dehydrated/releases/download/v$(DEHYDRATED_VERSION)
 
 DEHYDRATED_LICENSE = MIT
Signature · 1 line
2.21.0
#1 lore raw

PATCH 1/1 dehydrated: critical bump to 0.6.5

Quoted 8 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Arnout" == Arnout Vandecappelle (Essensium/Mind) <[email protected]> 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.

Quoted 8 lines

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.

Committed, thanks.

Quoted 4 lines

---
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

OK, I'll cherry pick it when I sync 2019.02.x with master later this week.

Signature · 1 line
Bye, Peter Korsgaard
#2 lore raw

PATCH 1/1 dehydrated: critical bump to 0.6.5

In reply to Arnout Vandecappelle (Essensium/Mind)
Quoted 6 lines · On Mon, 19 Aug 2019 18:37:49 +0200 "Arnout Vandecappelle (Essensium/Mind)"…

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.

Quoted 8 lines

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.

Commit title should have been prefixed with "package/dehydrated" :-)

Thanks,

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
#3 lore raw

PATCH 1/1 dehydrated: critical bump to 0.6.5

In reply to Arnout Vandecappelle (Essensium/Mind)
Quoted 15 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Arnout" == Arnout Vandecappelle (Essensium/Mind) <[email protected]> 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.

Quoted 5 lines

---
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.

Signature · 1 line
Bye, Peter Korsgaard