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, 06 Feb 2019 10:43:40 +0000	[thread overview]
Message-ID: <37474D26-8F9B-495B-8B69-D6ECE8FCB2CC@ipfire.org> (raw)
In-Reply-To: <7675eb9f8a0bf6aebc16a97aaa16f2d57adbdf9b.camel@ipfire.org>

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

Hello guys,

Great news Stefan! I will have a look at the image as soon as I can.

You have an extra f at the end of the download URL. I am sure that everyone has noticed that already, but here is the correct url:

  https://nightly.ipfire.org/next-suricata/latest/x86_64/ipfire-2.21.x86_64-full-core128.iso

What are the next steps for development here? I guess fixing the bugs that the testers find and the few outstanding ones. When is an updater going to be worked on?

Best,
-Michael

> On 6 Feb 2019, at 09:57, Stefan Schantl <stefan.schantl(a)ipfire.org> wrote:
> 
> Hello Ville,
> 
> thanks for joining the testing team.
> 
> There is currently no update from an existing IPFire installation to
> the suricata containing one. So you have to create backups, do a fresh
> installation and then restore your backups.
> 
> If possible and some test hardware is available, please install the
> image on a different machine than your productive one.
> 
> Best regards,
> 
> -Stefan
> 
> 
>> Hello,
>> 
>> Thx for bringing this update!
>> 
>> Is it ok to update my stable version of ipfire core 126 or should I
>> install this suricata version and then use backups to get my data and
>> settings back?
>> 
>> -Ville-
>> 
>> 
>>> On 6 Feb 2019, at 10.58, Stefan Schantl <stefan.schantl(a)ipfire.org>
>>> wrote:
>>> 
>>> Hello list,
>>> 
>>> today im very happy to announce a new test image with the latest
>>> snapshot of the process bringing suricata to all of you.
>>> 
>>> The image is now hosted and provided by the nightly build feature
>>> (a
>>> big thanks to Michael for providing this) of IPFire, so if
>>> development
>>> goes on, every time a new image will be generated and easily can be
>>> downloaded.
>>> 
>>> The latest image always can be grabbed from here:
>>> 
>>> https://nightly.ipfire.org/next-suricata/latest/x86_64/
>>> 
>>> Direct link for downloading the ISO image:
>>> 
>>> https://nightly.ipfire.org/next-suricata/latest/x86_64/ipfire-2.21.x86_64-full-core128.isof
>>> 
>>> There is currently one known issue, that any kind of snort rules
>>> (sourcefire) currenty can not be downloaded, so you have to use the
>>> rulesets from emergingthreads for testing. This issue will be fixed
>>> with the next image provided by the nightly build service.
>>> 
>>> Thanks for downloading and testing, as usual please file any bugs
>>> to
>>> our bugtracker (https://bugzilla.ipfire.org) and share your
>>> feedback on
>>> this list.
>>> 
>>> Best regards,
>>> 
>>> -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-02-06 10:43 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <79FF884C-B36B-42F5-A620-F2636E3706FC@gmail.com>
2019-02-06  9:57 ` Stefan Schantl
2019-02-06 10:43   ` Michael Tremer [this message]
     [not found] <E1gf64O-0003zJ-Kt@smtprelay03.ispgateway.de>
2019-01-06 13:26 ` IPFire meets Suricata - Call for Tester Stefan Schantl
2018-11-29 19:43 IPFire meets Suricata - Call for tester 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
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

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=37474D26-8F9B-495B-8B69-D6ECE8FCB2CC@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