From mboxrd@z Thu Jan  1 00:00:00 1970
From: Peter =?utf-8?q?M=C3=BCller?= <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: Testing Core Update 118
Date: Tue, 30 Jan 2018 18:44:13 +0100
Message-ID: <20180130184413.5a0b8552.peter.mueller@link38.eu>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1013842928632723335=="
List-Id: <development.lists.ipfire.org>

--===============1013842928632723335==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello,

I installed the Core Update 118 (beta) a few minutes ago:

IPsec N2N		WORKS
NRPE			WORKS
Squid			WORKS
WebUI			WORKS
Snort (IDS)		WORKS

Currently, there are these two (minor) issues:
(a) A patch of mine (marking 3DES and 1024 bit DH keys
as weak, see: https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommit;h=3D6fc0f=
5eb92c51067f79cf195d9c0e584556b29a7)
seems not to be applied. Maybe forgot to ship?

(b) Changing the remote syslogging settings does
not cause a crash anymore (this is fixed). However,
changing protocol to "TCP" does not change anything
in the configuration @ /etc/syslog.conf . Mea culpa,
I've got to have a look at this *again*, but at least
we do not have the segfault anymore.

Apart from that, everything changed in 118 seems to work.

Best regards,
Peter M=C3=BCller

--===============1013842928632723335==--