From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] openvpn: Update to version 2.5.8
Date: Mon, 21 Nov 2022 09:13:28 +0000 [thread overview]
Message-ID: <8A84D2F1-64E3-4F97-AA1B-F1637C494E70@ipfire.org> (raw)
In-Reply-To: <57828c2b-3f45-8fc2-e860-03e36d9f1d07@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2298 bytes --]
> On 21 Nov 2022, at 08:27, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>
>
>> - Update from version 2.5.7 to 2.5.8
>> - Update of rootfile not required
>> - Changelog
>> Version 2.5.8
>> tls-crypt-v2: bail out if the client key is too small
>> Remove useless empty line from CR_RESPONSE message
>> Allow running a default configuration with TLS libraries without BF-CBC
I am not sure how to read this. We would need to have BlowFish available for those people, who are still using it.
Can we test this before merging this patch, please?
>> Change command help to match man page and implementation
>> Fix OpenVPN querying user/password if auth-token with user expires
>> t_client: Allow to force FAIL on prerequisite fails
>> t_client.sh: do not require fping6
>> Preparing release 2.5.8
>> msvc: add branch name and commit hash to version output
>> Update the replay-window backtrack log message
>> Do not skip ERROR:/SUCCESS: response from management interface
>> Fix auth-token usage with management-def-auth
>> Allow a few levels of recursion in virtual_output_callback()
>> Ensure --auth-nocache is handled during renegotiation
>> Purge auth-token as well while purging passwords
>> Do not copy auth_token username to itself
>>
>> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
>> ---
>> lfs/openvpn | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/lfs/openvpn b/lfs/openvpn
>> index 0483ac311..db2246206 100644
>> --- a/lfs/openvpn
>> +++ b/lfs/openvpn
>> @@ -24,7 +24,7 @@
>>
>> include Config
>>
>> -VER = 2.5.7
>> +VER = 2.5.8
>>
>> THISAPP = openvpn-$(VER)
>> DL_FILE = $(THISAPP).tar.gz
>> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>>
>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>>
>> -$(DL_FILE)_BLAKE2 = f5db74445d080f191b09a4ff5512712973fa6c3a6662479e11d2398e5e01c45eba5d50faa3301c715066dd0eb2f7d8702ceefc68d9edb1af264ec699710f8e5c
>> +$(DL_FILE)_BLAKE2 = d029f6facd94a82aa28765cab340130dd4e5a4ffc2e0ccf3bf4888aee52d337126c21fdd7304dbaad5fe67d0a1f8d44e5a3c44801dcfa935aef200675ac5167f
>>
>> install : $(TARGET)
>>
prev parent reply other threads:[~2022-11-21 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 21:48 Adolf Belka
2022-11-21 8:27 ` Peter Müller
2022-11-21 9:13 ` Michael Tremer [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=8A84D2F1-64E3-4F97-AA1B-F1637C494E70@ipfire.org \
--to=michael.tremer@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