From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Betatest Guardian 2.0
Date: Tue, 19 Jul 2016 12:01:13 +0200 [thread overview]
Message-ID: <1468922473.13947.13.camel@ipfire.org> (raw)
In-Reply-To: <578DD360.9000802@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 4596 bytes --]
Hello Daniel,
thanks for testing and your feedback.
> Hi
> At first everything seems to wok as designed.
>
> First thing I found...
> If I add an IP to the ignorelist it also works as designed. But if
> I
> remove it the Webif didn't show it any more but the IP seems to be
> still
> ignored until I restart the Guardian.
>
Seems to be a bug, I'll have a look on the code.
> Next thing.
> The owncloud parser don't work. Please tell me what you need.
Nothing at all, I will have to do a deeper look into the non working
code. I'll post the updated parser to the mailinglist so the new one
can be tested.
>
> I wish me a restart button on the webif.
Why do you think to need such a button. Guardian is designed to reload
and communicate with the WUI over a Socket connection. So there should
not be any need to do a restart of guardian, except an update of the
daemon has been installed.
>
> -
> Daniel
Best regards,
-Stefan
>
>
>
> Am 18.07.2016 um 16:01 schrieb Stefan Schantl:
> >
> > Hello mailing list followers,
> >
> > this is the official release announcement for the first beta
> > release of
> > the new Guardian 2.0 approach.
> >
> >
> > - What are the differences to the current version of guardian
> > (legacy)
> > and the first approach of guardian 2.0?
> >
> > The most important difference is, that the new version of Guardian
> > 2.0
> > completely has been re-written from scratch and released under the
> > terms of the GPLv3. The legacy version of guardian is not
> > maintained
> > anymore by it's developer and the software has been released
> > without
> > any license details at all.
> >
> > Guardian 2.0 has a very modular code base and has been designed as
> > a
> > multi-threaded application. This allows a parallel parsing of all
> > monitored logfiles and faster actions, if one of the used modules
> > detects an attack.
> >
> > A very important difference to the legacy version is the support of
> > configuring and managing the entire service through the IPFire
> > webinterface. The entire configuration, managing of current blocked
> > hosts, unblocking them or editing the ignored hosts list now can be
> > done in a graphical way.
> >
> > The legacy version of guardian only supported parsing snort alerts.
> > HTTPD and SSH support has been patched by the IPFire development
> > team
> > some time ago. Guardian 2.0 supports all of them out of the box and
> > includes a filter to detect owncloud login brute-force attempts. As
> > a
> > benefit of the new modular design, additional filters easily can be
> > added.
> >
> > Guardian 2.0 is able to reload it's configuration, reloading
> > the ignore list during runtime and handle, if the logfiles will get
> > rotated by logrotate. This actions can be called by using the
> > webinterface or from the command line interface by using
> > "guardianctrl".
> >
> > These are just a handful of the changes and benefits which comes
> > with
> > Guardian 2.0, a complete list would be to long for this mailing
> > list.
> >
> >
> > - How to join testing?
> >
> > To get part of the testing team, simple navigate to http://people.i
> > pfir
> > e.org/~stevee/guardian-2.0/ and download the latest tarball
> > (currently
> > 002). Please take care to download the correct one, based on your
> > used
> > architecture. The i585 packages are for 32Bit installations of
> > IPFire,
> > the x86_64 packages only can be used on 64Bit installations.
> >
> > Put the downloaded file on your IPFire test system and extract the
> > package by using "tar -xvf guardian-2.0-002.<arch>.tar.gz -C /".
> >
> > The final installation step would be to regenerate the language
> > cache
> > by executing "update-lang-cache" on the console.
> >
> > From now you can find a new menu item called "Guardian" in your
> > "Service" menu after you have logged-in into your IPFire's
> > webinterface.
> >
> > Documentation can be found on the IPFire wiki: http://wiki.ipfire.o
> > rg/e
> > n/addons/guardian/start#the_guardian_20_addon
> >
> >
> > - Where to post bugs reports or provide feedback?
> >
> > If you find any bugs, please report them as usual on the IPFire
> > bugtracker, which can be found at https://bugzilla.ipfire.org.
> >
> > To provide feedback or to join a discussion, please send your mails
> > to
> > "development(a)lists.ipfire.org" (Please register first at http://lis
> > ts.i
> > pfire.org if not yet done).
> >
> > The source code can be found at http://git.ipfire.org/?p=people/ste
> > vee/
> > guardian.git;a=summary
> >
> >
> > Happy testing,
> >
> > -Stefan
> >
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-19 10:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 14:01 Stefan Schantl
2016-07-19 7:14 ` Daniel Weismüller
2016-07-19 10:01 ` Stefan Schantl [this message]
2016-07-20 13:37 ` Stefan Schantl
2016-07-20 13:33 ` Stefan Schantl
2016-07-20 14:28 ` Matthias Fischer
2016-07-21 11:25 ` Matthias Fischer
2016-07-21 11:28 ` Michael Tremer
2016-07-21 13:07 ` Matthias Fischer
2016-07-21 15:57 ` Matthias Fischer
2016-07-21 19:05 ` Flying Trashcan
2016-07-21 19:52 ` Flying Trashcan
2016-07-21 21:07 ` Matthias Fischer
2016-07-22 20:28 ` Matthias Fischer
2016-07-22 22:23 ` Matthias Fischer
2016-07-26 15:10 ` Michael Tremer
2016-07-26 18:31 ` Matthias Fischer
2016-07-28 17:41 ` Stefan Schantl
2016-07-28 10:47 ` Stefan Schantl
2016-07-28 18:05 ` Stefan Schantl
2016-07-29 16:20 ` Matthias Fischer
2016-07-30 19:06 ` Matthias Fischer
[not found] <1468920284.13947.5.camel@ipfire.org>
2016-07-19 12:54 ` Matthias Fischer
2016-07-19 17:26 ` Stefan Schantl
2016-07-19 18:01 ` Matthias Fischer
[not found] <8916bfc3-2af6-af48-992b-b014d51a405a@ipfire.org>
2016-08-06 19:39 ` Michael Tremer
2016-08-06 22:41 ` Matthias Fischer
2016-08-24 12:36 ` Daniel Weismüller
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=1468922473.13947.13.camel@ipfire.org \
--to=stefan.schantl@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