From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Upcoming telephone conference regarding IDS situation in 2.x
Date: Thu, 12 Jul 2018 09:53:05 +0100 [thread overview]
Message-ID: <c1ec0c039ef6fb9910af74fc53bd7b60e72c95bf.camel@ipfire.org> (raw)
In-Reply-To: <1917827b-81ab-9130-79e8-8c85b8cf8872@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 2011 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On Wed, 2018-07-11 at 21:48 +0200, Peter Müller wrote:
> Hello *,
>
> just for those who are interested: There will be a telephone conference
> on 20:00 CEST next Monday (16.07.) in conference room 1 regarding the IDS
> situation in IPFire 2.x .
>
> Over time, some bugs have been collected and we need to decide about
> the next step. On possibility is to keep Snort in 2.x and fix these bugs
> so we have a clean setup there. The other way Stefan and myself worked
> out is to switch to Suricata in 2.x (for 3.x, it is already settled, so
> we have to deal with it sooner or later) and use a completely new IDS CGI.
>
> For the latter, Stefan already did some work:
> https://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=shortlog;h=refs/heads
> /ids.cgi-new
>
> In case anybody is interested, please join.
>
> @Michael: Raise hand in case room 1 is occupied on this evening. Thanks. :-)
No, we don't have that many concurrent conferences going on at the same time :)
The number to dial in is 901.
Best,
- -Michael
>
> Thanks, and Best regards,
> Peter Müller
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE5/rW5l3GGe2ypktxgHnw/2+QCQcFAltHFvEACgkQgHnw/2+Q
CQdg2Q/9Ge7z+zA3AlVfpKh6gq/LZBd4W2bWWbjHPA/BVFT/cX0lJSzK1dSm4+Oq
iwboBv9tbkxEBNDVY2+Bufei7CCQo6Zj+cVrAyqG5FF8aqkDX0QP1xVcJzNm/Xf9
HFjpmc2c+cmsZa4Z9WSsQuld51A5i+E/ZCFh+H9l6vGw4vPRSRq7kn0nMoRPYVsO
9maJXYD+PiM70t7OjLIwpldQKgL9/oZDbpoANwBmhJHp0u9aHrnw3J3FdKtmm/nh
TByql27CEPvP7dvyz03JO5U60f5IcyBoHG808rvquKB/fnOtGK8JAfYzlXzuR5qD
mjwiAry6OLr5GeVTwPLrMGQMu1JBxgee7Xcnd6wp3l9BMC1BUhRCFAyvnx+63eIY
OxDStgY0S9zxOkrIV0ZKTLTPgQ635eR+v7eaen1evak7yiV+yJ6zw4c1DBI466qs
zplt4nbYMn41G65tCr6LCoIfghv0R8oA7uwdET5G6Hgb2yaVGTxbK5jPjSeYs30f
ME9Wab7llC9dGflYiBHCcXXWTHOZhV7BAwOXwGIdXklacpNkvkiaXHzY6Lfk9sdB
mBsE+kd9mSpP5tAjw2EAqpGds9ClGw93xMRMOrQ6ROvaxk5jzdhszPw/2wSlnMnL
FKmJWt1J3vkg0WeUBKh7agsOXZJS0BQefLL6M9Ft34UVMRP0dz0=
=5RHb
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2018-07-12 8:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 19:48 Peter Müller
2018-07-12 8:53 ` Michael Tremer [this message]
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=c1ec0c039ef6fb9910af74fc53bd7b60e72c95bf.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