From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Testing Core Update 118
Date: Tue, 30 Jan 2018 20:57:47 +0000 [thread overview]
Message-ID: <1517345867.2586.75.camel@ipfire.org> (raw)
In-Reply-To: <20180130184413.5a0b8552.peter.mueller@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]
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=6fc0f5eb92c5
> 1067f79cf195d9c0e584556b29a7)
> seems not to be applied. Maybe forgot to ship?
Yes, ovpnmain.cgi was not in the updater. I added it.
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=3925a0db6cc0ca91fe34eb7c0366f72b0af39ab6
However, it appears that our syslog daemon doesn't support TCP at all.
...
-Michael
>
> Apart from that, everything changed in 118 seems to work.
>
> Best regards,
> Peter Müller
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-30 20:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 17:44 Peter Müller
2018-01-30 20:57 ` Michael Tremer [this message]
[not found] <1517416528.2586.92.camel@ipfire.org>
2018-02-01 8:41 ` ummeegge
2018-02-01 11:37 ` Michael Tremer
2018-02-01 14:43 ` ummeegge
2018-02-01 15:16 ` Michael Tremer
2018-02-02 19:49 ` ummeegge
2018-02-03 19:42 ` ummeegge
2018-02-06 9:37 ` ummeegge
2018-02-06 16:30 ` 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=1517345867.2586.75.camel@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