From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4ZKmN018Pzz3325 for ; Sat, 22 Mar 2025 17:22:24 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R10" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4ZKmMw43R2z32vy for ; Sat, 22 Mar 2025 17:22:20 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4ZKmMv536pz8q4 for ; Sat, 22 Mar 2025 17:22:19 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1742664139; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=2irNzDQqRkIyYzoGhAzUxLb6uy/3jTYVtHzsJ8LvaEg=; b=/bliLGSVLAqLuGBuv+QsKI7WOghf40xjYm9qBRUu6NC0/Ql4LRSHdPXlPByDnK3EGQhm2K BR2lXtBhMaxCqlDw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1742664139; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=2irNzDQqRkIyYzoGhAzUxLb6uy/3jTYVtHzsJ8LvaEg=; b=dDXDLle+q55yY+fH6mYNw5KeYrfYG7IrK2h82fdO3r6BGkxTJ4IEFTBiWfNl9n/TfCpTBJ b2ZT0dSXA5hR/R48cKt+8dRqJ+1nrB1L2Dq22H8cHdPioQWAoUHJ5y4T515ku0VShUK1D8 R6SdP1pZEdKZOOo15/xH4IHLYf3GS7i0ClQO60LkNxrw8yhDTtYkpBeRAs2vBlEZqB676u WNcSW7uH31jQv2WaD75ydR8geke4Ghk6Y0yXeIxTauKsa0IWRCoXN6C/GVllGuyhtSzp2J CU0qR0S6ayLjaw5u4YpfBo4qZfXX7cxNW4TykemCgZIR5A2OJkG38eImWbTmOQ== Message-ID: <2c4d9fcd-6cde-4bcd-a65d-815d7d283dc4@ipfire.org> Date: Sat, 22 Mar 2025 18:22:15 +0100 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Subject: Re: IPFire 2.29 - Core Update 193 is available for testing To: development@lists.ipfire.org References: <174238111584.1720815.10275774082881760962.ipfire@ipfire.org> Content-Language: en-GB From: Adolf Belka In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi, I have tested my fix for bug13737 and found that it works fine when a new ipsec x509 root/host certificate set is created. However it doesn't work for existing sets as they already have the serial file contents at 01. I forgot to add in some code for the update.sh file to update existing root/host certificates with serial file contents at 01 to 02. I will put a patch together and submit it for merging and testing. Regards, Adolf. On 21/03/2025 13:10, Michael Tremer wrote: > Hello Adolf, > >> On 20 Mar 2025, at 17:40, Adolf Belka wrote: >> >> Hi All, >> >> My first findings from CU193 Testing. > > Thank you for testing. > >> The IPBlocklist sources file and the backup.pl file with the changes related to removal of the ABUSECH blocklist, did not get into the filelist file and so that blocklist was not removed. > > Thank you. I pushed a commit for this. > >> I tested out ipsec. >> A working PSK and cert connection from CU192 were both tested out with CU193 Testing. >> Both worked in CU192 and also worked without issues when IPFire was updated to CU193 Testing. >> >> I then created a new ipsec cert connection and tested that out and it worked but it did not use the post quantum cipher. >> >> Strongswan-6.0.0 is also on my laptop but I am using Network Manager with a Strongswan plugin and that might not yet be updated with the post quantum ciphers. > > I think this might be quite difficult to test on a client, because NetworkManager will also need to support this and I am not sure how fast they will be. > > I did however test this myself on a N2N connection and it works fine. Sadly there is no different feeling to those connections as it only affects the handshake. We don’t have to worry about any decreased throughput because of more complex cryptography. > >> My laptop and IPFire negotiated a cipher and that connection then worked. >> >> The other thing that might be getting in the way is that all the certs currently created in IPSec are legacy based ones,m even if the Root/Host certificate has been re-created to have the more secure version with openssl-3.x >> >> I raised a bug on this a while back. >> https://bugzilla.ipfire.org/show_bug.cgi?id=13808 >> >> This came about when we updated to OpenSSL-3.x. I added in the legacy options into the openssl commands in the ovpnmain.cgi page and did the same thing to the vpnmain.cgi page for IPSec. >> >> Then in the ovpnmain.cgi page I added in the check if the root/host x509 set was legacy or not and then only used the legacy option if it was. >> >> However, I never went back to the vpnmain.cgi page to update that to only use -legacy if the root/host x509 was legacy. >> So currently all client certs are legacy, even if the root/host x509 is not. >> >> I have assigned that ipsec bug to myself and it will be something I will have a go at sometime soon. > > I don’t like that the entire X.509 situation is becoming more of a nightmare with every single day that is passing... > >> However, main thing, the change to strongswan-6.0.0 has not negatively impacted the ipsec operation. All existing connections, at least the ones I had, worked after the CU193 Testing update. > > Great! I can confirm the same. > > -Michael > >> Regards, >> Adolf. >> >> On 19/03/2025 11:57, IPFire Project wrote: >>> Hello Community! Only a few days after releasing the latest update, we are excited to begin testing the next one. It comes with support for Post-Quantum Cryptography in IPsec as well as a new toolchain and a lot of bug and security updates. >>> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ >>> IPFire_ >>> IPFire 2.29 - Core Update 193 is available for testing >>> Hello Community! Only a few days after releasing the latest update, we are excited to begin testing the next one. It comes with support for Post-Quantum Cryptography in IPsec as well as a new toolchain and a lot of bug and security updates. >>> Read The Full Post On Our Blog >>> The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstraße 8, 45711 Datteln, Germany >>> Unsubscribe >> >> > >