public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] dehydrated: Update to version 0.7.1
Date: Fri, 18 Nov 2022 23:51:21 +0100	[thread overview]
Message-ID: <20221118225121.1361904-1-adolf.belka@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2054 bytes --]

- Update from version 0.7.0 to 0.7.1
- Update of rootfile not required
- Changelog
    ## [0.7.1] - 2022-10-31
	## Changed
		- `--force` no longer forces domain name revalidation by default, a new argument `--force-validation` has been added for that
		- Added support for EC secp521r1 algorithm (works with e.g. zerossl)
		- `EC PARAMETERS` are no longer written to privkey.pem (didn't seem necessary and was causing issues with various software)
	## Fixed
		- Requests resulting in `badNonce` errors are now automatically retried (fixes operation with LE staging servers)
		- Deprecated `egrep` usage has been removed
	## Added
		- Implemented EC for account keys
		- Domain list now also read from domains.txt.d subdirectory (behaviour might change, see docs)
		- Implemented RFC 8738 (validating/signing certificates for IP addresses instead of domain names) support (this will not work with most public CAs, if any!)

Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
 lfs/dehydrated | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lfs/dehydrated b/lfs/dehydrated
index b6ad9949a..7cd92076b 100644
--- a/lfs/dehydrated
+++ b/lfs/dehydrated
@@ -26,7 +26,7 @@ include Config
 
 SUMMARY    = A client for signing certificates with an ACME server
 
-VER        = 0.7.0
+VER        = 0.7.1
 
 THISAPP    = dehydrated-$(VER)
 DL_FILE    = $(THISAPP).tar.gz
@@ -34,7 +34,7 @@ DL_FROM    = $(URL_IPFIRE)
 DIR_APP    = $(DIR_SRC)/$(THISAPP)
 TARGET     = $(DIR_INFO)/$(THISAPP)
 PROG       = dehydrated
-PAK_VER    = 4
+PAK_VER    = 5
 
 DEPS       =
 
@@ -48,7 +48,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = 35a3b0b7592126ca65003a6c9eb8934a76584710d028057e5add7f77bb2fa3799e89a060306da3b98a62d291229a2a78f23e0f95f19e033796aee31e97b94488
+$(DL_FILE)_BLAKE2 = 0b287537206936ceff33bde8bbb8ab7b13f28bf58cd29c898348db0cf5a83157fed4535da218ac48a810a93b99474e96334a27c062c157e2f164b0e516b47111
 
 install : $(TARGET)
 
-- 
2.38.1


             reply	other threads:[~2022-11-18 22:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 22:51 Adolf Belka [this message]
2022-11-19 11:51 ` Michael Tremer

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=20221118225121.1361904-1-adolf.belka@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /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