From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: IPFire 2.29 - Core Update 190 is available for testing Date: Tue, 03 Dec 2024 13:50:22 +0100 Message-ID: <23ab7a4e-e5b9-484b-8ff9-9883b8ea2166@ipfire.org> In-Reply-To: <173297648318.584589.10152294806985753314.ipfire@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3982251804060376989==" List-Id: --===============3982251804060376989== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi All, First feedback on CU190 Testing. I have not found any problems so far. I have tested the OpenVPN roadwarrior and net2net connections and all=20 worked well. I also cleared the x509 certificate set and created from new (as there=20 were problems in the past with that) and a new x509 set could be created=20 without any issues. Restore from previous backup also worked without any issues. All graphs look to be running okay. Bug13029 - IPSec problem when PSK had a comma in it was tested and the=20 base64 encoding is working as intended. Existing PSK's stay as they are.=20 If a new PSK is defined or an existing one edited then the PSK is base64=20 encoded. In all cases the operation continues with the base64 encoding changes=20 being totally transparent. A PSK with any character, except the single quotation mark, can now be=20 used in the PSK. Tested out with a PSK with back ticks, hash symbol and=20 double quotation marks and the IPSec PSK connection was made without any=20 issues. Bug13074 verified to now have the collectd.d directory for custom=20 variations. Actual custom variations not tested so far. Bug13762 ssh login details not being shown in system logs verified to be=20 fixed. Both sshd and sshd-session lines from the logs are now included=20 in the system logs display. Will continue testing but so far looks very good to me. Regards, Adolf. On 30/11/2024 15:37, IPFire Project wrote: > Dear Community, It is time for the last push of the year: The upcoming=20 > release of IPFire is ready to be tested by you, our awesome community.=20 > It comes with a refreshed kernel and includes a lot of changes that have=20 > been developed at the recent IPFire Developer Meetup. It is scheduled to=20 > be the last update for the year, so let's make it an extra special one=20 > before we all sign off for the holidays. > =E2=80=8C=C2=A0=E2=80=8C=C2=A0=E2=80=8C=C2=A0=E2=80=8C=C2=A0=E2=80=8C=C2=A0= =E2=80=8C=C2=A0=E2=80=8C=C2=A0=E2=80=8C=C2=A0=E2=80=8C=C2=A0=E2=80=8C=C2=A0= =E2=80=8C=C2=A0=E2=80=8C=C2=A0=E2=80=8C=C2=A0=E2=80=8C=C2=A0=E2=80=8C=C2=A0= =E2=80=8C=C2=A0=E2=80=8C=C2=A0=E2=80=8C >=20 >=20 > IPFire_ >=20 >=20 > IPFire 2.29 - Core Update 190 is available for testing >=20 > Dear Community, It is time for the last push of the year: The upcoming=20 > release of IPFire is ready to be tested by you, our awesome community.=20 > It comes with a refreshed kernel and includes a lot of changes that have=20 > been developed at the recent IPFire Developer Meetup. It is scheduled to=20 > be the last update for the year, so let's make it an extra special one=20 > before we all sign off for the holidays. >=20 > Read The Full Post On Our Blog core-update-190-is-available-for-testing?=20 > utm_medium=3Demail&utm_source=3Dblog-announcement> >=20 > The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstra=C3=9Fe 8, 457= 11=20 > Datteln, Germany >=20 > Unsubscribe >=20 --=20 Sent from my laptop --===============3982251804060376989==--