kumquat-buildroot/package/dehydrated/dehydrated.hash

# Locally computed after verifying
# 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  10aabd0027450bc70a18e49acaca7a9697e0cfb92368d3e508b7a4d6d69bfa35 dehydrated-0.6.5.tar.gz
# License, locally computed
sha256  b4583b7dd07e3e2a08906de38e7e329d41f921ed9dcb6310b3886e013a6b8723  LICENSE
package/dehydrated: new package dehydrated is an ACME client written in bash. It should be able to run under zsh as well, but this hasn't been tested so it isn't enabled for now. Normally, we would want an init script to start dehydrated, and an example configuration file. However, it is very difficult to do this in a generic way in Buildroot: - we normally don't have cron running; - we have no standard location for webroot; - we have no standard location for certificates; - we have no standard way to restart/reload the webserver. So instead, provide brief documentation of how to use dehydrated in the help text. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> 2018-06-18 14:13:09 +02:00			`# Locally computed after verifying`
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. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com> 2019-08-19 18:37:49 +02:00			`# https://github.com/lukas2511/dehydrated/releases/download/v0.6.5/dehydrated-0.6.5.tar.gz.asc`
package/dehydrated: new package dehydrated is an ACME client written in bash. It should be able to run under zsh as well, but this hasn't been tested so it isn't enabled for now. Normally, we would want an init script to start dehydrated, and an example configuration file. However, it is very difficult to do this in a generic way in Buildroot: - we normally don't have cron running; - we have no standard location for webroot; - we have no standard location for certificates; - we have no standard way to restart/reload the webserver. So instead, provide brief documentation of how to use dehydrated in the help text. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> 2018-06-18 14:13:09 +02:00			`# with key 3C2F2605E078A1E18F4793909C4DBE6CF438F333 from https://keybase.io/lukas2511`
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. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com> 2019-08-19 18:37:49 +02:00			`sha256 10aabd0027450bc70a18e49acaca7a9697e0cfb92368d3e508b7a4d6d69bfa35 dehydrated-0.6.5.tar.gz`
package/dehydrated: new package dehydrated is an ACME client written in bash. It should be able to run under zsh as well, but this hasn't been tested so it isn't enabled for now. Normally, we would want an init script to start dehydrated, and an example configuration file. However, it is very difficult to do this in a generic way in Buildroot: - we normally don't have cron running; - we have no standard location for webroot; - we have no standard location for certificates; - we have no standard way to restart/reload the webserver. So instead, provide brief documentation of how to use dehydrated in the help text. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> 2018-06-18 14:13:09 +02:00			`# License, locally computed`
			`sha256 b4583b7dd07e3e2a08906de38e7e329d41f921ed9dcb6310b3886e013a6b8723 LICENSE`