public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire meets Suricata - Call for tester
Date: Wed, 02 Jan 2019 15:54:35 +0000	[thread overview]
Message-ID: <A9482F5F-111C-4873-8913-33D85B244420@ipfire.org> (raw)
In-Reply-To: <9795d2668f4aece36cd937e9f54b134c339da17a.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 3203 bytes --]

Hello Stefan,

Thanks for baking a new image. I just installed this and gave it a little test.

I will start with some comments on the UI:

* The error messages are a bit shouty. “No ruleset available, PLEASE DOWNLOAD ONE!!!111!!!” Is not really how these usually go.

The is two ways how to solve this: a) rephrase the messages and b) avoid that the user is shown this anyways. For example: grey out the enable checkbox when no ruleset has been downloaded and show a small note that this is a requirement.

* I think the top box can be merged with the settings box. There is too many headlines and this is rather confusing. It is one box in all other add-ons.

* It is not possible to click the Download button for rules when Save hasn’t been clicked before. That doesn’t make much sense.

* Downloading rules does not work. The log file says that no ruleset was selected although it was. Doesn’t work with any.

* In the German translation the word “Regelset” and “Regelsatz” are being used. I think the latter is the correct version.

So, I could not get this to work. What should I do?

-Michael

> On 1 Jan 2019, at 13:32, Stefan Schantl <stefan.schantl(a)ipfire.org> wrote:
> 
> Hello list followers,
> 
> a very happy new year to all of you!
> 
> I had some free time during the christmas days and backed a new testing
> image for suricata:
> 
> https://people.ipfire.org/~stevee/suricata/Images/ipfire-2.21.x86_64-suricata-beta4-full-core127.iso
> 
> It contains a lot of bug fixes and improvements suggested on this list.
> 
> As usual please do a lot of testing and report back any issues and
> suggestions.
> 
> Thanks in advance,
> 
> -Stefan
> 
> 
>> Hello list followers,
>> 
>> some time ago development for the new implementation of the Intrusion
>> Detection functionality in IPFire has been started.
>> 
>> The main goal, in a nutshell, was to give IPFire a modern, feature-
>> rich 
>> and user-friendly Intrusion Detection Engine. During this progress,
>> the
>> detection framework has been replaced - now suricata is used instead
>> of
>> snort.
>> 
>> Suricata uses a very modern and multi-threaded detection engine with
>> support to perform actions on malicious traffic. So it provides the
>> functionality of detecting any kind of intrusion attempts and the
>> ability of guardian to block them under the same hood.
>> 
>> It was a lot of work, but finaly I'm happy to announce the first test
>> version. It is almost feature complete and without any kind of bigger
>> issues.
>> 
>> Because Intrusion Detection is a key feature of a firewall system, a
>> lot of testing is required until the new implementation can become
>> part
>> of IPFire - therefore we need your help!
>> 
>> Download the test image (
>> https://people.ipfire.org/~stevee/suricata/Images/), do a lot of hard
>> testing and provide your feedback or suggestions on the develoment
>> mailing list (https://lists.ipfire.org/mailman/listinfo/development).
>> 
>> If you find any bugs please file them in the IPFire Bugtracker (
>> https://bugzilla.ipfire.org/).
>> 
>> Many thanks in advance,
>> 
>> -Stefan


  reply	other threads:[~2019-01-02 15:54 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-29 19:43 Stefan Schantl
2018-12-11 20:53 ` Peter Müller
2018-12-12 20:54   ` Peter Müller
2018-12-16 20:28     ` Peter Müller
2018-12-17 14:21       ` Stefan Schantl
2018-12-17 17:05         ` Michael Tremer
2018-12-17 19:08           ` Stefan Schantl
2018-12-19 16:30             ` Michael Tremer
2018-12-20 13:03               ` Stefan Schantl
2018-12-20 14:05                 ` Michael Tremer
2018-12-21 16:03                   ` Tim FitzGeorge
2018-12-25 19:17                     ` Stefan Schantl
2018-12-25 21:56                       ` Michael Tremer
2018-12-25 19:03                   ` Stefan Schantl
2019-01-01 13:32 ` Stefan Schantl
2019-01-02 15:54   ` Michael Tremer [this message]
2019-02-06  8:58 ` Stefan Schantl
2019-02-14 14:28 ` Stefan Schantl
2019-02-14 15:20   ` ummeegge
2019-02-14 18:01   ` Matthias Fischer
2019-02-14 21:49     ` Stefan Schantl
2019-02-14 23:16       ` Matthias Fischer
2019-02-14 23:36   ` Mentalic
2019-02-15  7:51     ` Stefan Schantl
2019-02-15  0:03   ` Mentalic
2019-02-15  7:54     ` Stefan Schantl
2019-02-17 11:58 ` Stefan Schantl
2019-02-17 12:59   ` Michael Tremer
2019-02-17 19:57     ` Stefan Schantl
2019-02-18 11:44       ` Michael Tremer
2019-02-18 13:09         ` Stefan Schantl
2019-03-03 11:37   ` ummeegge
2019-03-03 18:48     ` Stefan Schantl
2019-03-04  6:28       ` ummeegge
2019-02-18 13:16 ` Stefan Schantl
2019-02-18 22:11   ` Mentalic
2019-02-19 11:33     ` Stefan Schantl
2019-02-19 22:12       ` Mentalic
2019-02-19 23:22         ` Mentalic
2019-02-20  7:55           ` Stefan Schantl
2019-02-21 21:56             ` Mentalic
2019-02-22 10:21               ` Michael Tremer
2019-02-22 11:08                 ` Stefan Schantl
2019-02-22 10:59               ` Stefan Schantl
2019-02-22 18:40                 ` Mentalic
2019-02-20  7:19         ` Stefan Schantl
2019-03-03 14:39 ` Stefan Schantl
2019-03-03 17:33   ` Mentalic
2019-03-04 19:54     ` Mentalic
2019-03-05  9:31       ` Michael Tremer
     [not found] <E1gf64O-0003zJ-Kt@smtprelay03.ispgateway.de>
2019-01-06 13:26 ` IPFire meets Suricata - Call for Tester Stefan Schantl
     [not found] <79FF884C-B36B-42F5-A620-F2636E3706FC@gmail.com>
2019-02-06  9:57 ` IPFire meets Suricata - Call for tester Stefan Schantl
2019-02-06 10:43   ` 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=A9482F5F-111C-4873-8913-33D85B244420@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