Yeah this a bit unfortunate now, but hey... Things happen.
I wouldn't mind changing to rsyslog, but would this be just a drop-in replacement or cause some serious work?
-Michael
On Wed, 2018-01-31 at 05:22 +0100, Peter Müller wrote:
Hello Michael,
Hi,
On Tue, 2018-01-30 at 18:44 +0100, Peter Müller wrote:
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=ipfire-2.x.git;a=commit;h=6fc0f5eb 92c5 1067f79cf195d9c0e584556b29a7) seems not to be applied. Maybe forgot to ship?
Yes, ovpnmain.cgi was not in the updater. I added it.
Could you add vpnmain.cgi, too? It seems to be also forgotten.
Not sure if Arne will re-package it.
???
(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.
Yes, but the sed syntax was butchered. I fixed in a new commit:
https://cgit.ipfire.org/ipfire-2.x.git/commit/?h=next&id=3925a0db6cc0ca9... e34eb7c0366f72b0af39ab6
However, it appears that our syslog daemon doesn't support TCP at all.
You are right; I missed that during testing since I was using rsyslog all the time, which is able to log via TCP. Shit.
So this function is currently useless. Is switching to rsyslog an option or would that be too complex? (Seems to be more active than sysklogd anyway.)
I know shipping new frondend features before backend is ready is the wrong order, but as mentioned already, it really slipped my mind.
Best regards, Peter Müller
...
-Michael
Apart from that, everything changed in 118 seems to work.
Best regards, Peter Müller