From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Feedback on testing of openvpn connections with openssl-3.2.0
Date: Wed, 17 Jan 2024 10:22:43 +0000 [thread overview]
Message-ID: <1B2B787D-8084-4856-B07F-AE4EA2C04723@ipfire.org> (raw)
In-Reply-To: <b5dbd16c-5626-4660-95c7-79b7c927f5b8@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]
Hello Adolf,
Thank you very much for testing.
I believe that I might have a small regression from OpenSSL 3.2.0 - at least I think it is that:
https://bugzilla.ipfire.org/show_bug.cgi?id=13527
Apache won’t start if a system has been upgraded for a long time and is using an older RSA key.
I could not find any indication in the change log of OpenSSL, but since we did not touch Apache itself in this update, I cannot come up with any other idea.
Since we are already using ECDSA keys as well as RSA keys, how about dropping the RSA keys altogether to solve this problem?
-Michael
> On 16 Jan 2024, at 14:18, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi All,
>
> At the last video call we agreed to test out openvpn and ipsec with the openssl-3.2.0 version that is in next.
>
> I cloned a vm and updated it to unstable (CU183) and ran my existing openvpn connections on it that had been created with an older version of openssl-3.x. Everything worked without any problems.
>
> I then created new connections with openssl-3.2.0 and tested them out. Again the connection was successfully made and I could access the remote green machine with no problems.
>
> So for openvpn there looks to be no issues with openssl-3.2.0 from my testing.
>
> Regards,
> Adolf.
>
> --
> Sent from my laptop
>
next prev parent reply other threads:[~2024-01-17 10:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 14:18 Adolf Belka
2024-01-17 10:22 ` Michael Tremer [this message]
2024-01-19 10:54 ` Adolf Belka
2024-01-19 10:44 ` Adolf Belka
2024-01-19 8:50 ` Peter Müller
2024-01-19 11:50 ` Adolf Belka
2024-01-19 16:25 ` 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=1B2B787D-8084-4856-B07F-AE4EA2C04723@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