From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Fischer To: development@lists.ipfire.org Subject: Re: Betatest Guardian 2.0 Date: Thu, 21 Jul 2016 23:07:42 +0200 Message-ID: <326d647f-04cf-8b02-93fc-55e764b973f8@ipfire.org> In-Reply-To: <987FF3D7-DD47-4EBB-BBB9-82F3A9604BE4@gmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0784772504382676909==" List-Id: --===============0784772504382676909== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, Sounds interesting. So I thought I take a little test... Initial RAM-Usage: 14334 KB First I just switched logging, did nothing else: syslog =3D> file =3D> 22726 KB file =3D> syslog =3D> 31117 KB syslog =3D> file =3D> 39507/47898 KB (RAM suddenly altered. Why? No idea.) file =3D> syslog =3D> 56289 KB Restarted through console: root(a)ipfire: /var/log/guardian # guardianctrl restart Stopping Guardian... Starting Guardian... Unable to continue: /usr/sbin/guardian is running [ WARN ] Hm? Stopped through console, no output, 'guardian' not found anymore, neither in GUI nor through console: root(a)ipfire: /var/log/guardian # ps ax | grep guardian 6962 pts/1 S+ 0:00 grep guardian Started through console and we're exactly where we started (14334 KB). The same happens if I switch the 'Priority-level' or the 'Firewall-Action'. Initial: 2 2 =3D> 3 =3D> 22723 KB 3 =3D> 2 =3D> 31112 KB Firewall-Action: Reject =3D> Drop =3D> 39501 KB Stop =3D> Start =3D> 14334 KB Interestingly, during MY (log-)switching, 'guardian' never stopped. HTH, Matthias On 21.07.2016 21:52, Flying Trashcan wrote: > I am now noticing that when I switch from Log facility =E2=80=9Cfile=E2=80= =9D to =E2=80=9Csyslog=E2=80=9D, Guardian Daemon stops and doesn=E2=80=99t re= start. Switching from syslog to file didn=E2=80=99t stop the service, only s= witching back to syslog from file. I can manually start the service and be b= ack to normal. Not a big deal, but if someone made the switch and didn=E2=80= =99t think to manually start the service, it could be left without running Gu= ardian. >=20 >=20 >=20 >=20 >> On Jul 21, 2016, at 4:25 AM, Matthias Fischer wrote: >>=20 >> Hi, >>=20 >> I mentioned this earlier, but it seems that 'guardian' has some kind of >> memory leak? >>=20 >> It started about two days ago with ~14 MB RAM. Then it jumped to ~34 MB, >> then to ~48 MB - today it suddenly uses 71 MB. >>=20 >> And if I start it on my testmachine (offline!) it uses ~90 MB. >>=20 >> Can someone confirm? >>=20 >> Besides this, its working without seen problems. >>=20 >> Best, >> Matthias >>=20 >> On 20.07.2016 15:33, Stefan Schantl wrote: >>> Hello testers, >>>=20 >>> I've uploaded a new test version (003). >>>=20 >>> Update or fresh install works like described in the announcement mail. >>>=20 >>> The Changelog can be found here: >>>=20 >>> http://people.ipfire.org/~stevee/guardian-2.0/Changelog.txt >>>=20 >>> At the moment I'm missing feedback for the following functions: >>>=20 >>> * Manually blocking / unblocking addresses. >>> * Dealing with the ignore list. >>> * Owncloud message parser. >>> * Logrotate, there should be an corresponding log entry in the guardian >>> logfile after rotation of the logfiles have been done. >>> * Reload of the ignore list after "Red" has been reconnected. There >>> also a corresponding log entry should be logged to the logfile and the >>> new "Red-address" should also be logged as part of the ignore list (If >>> you own an dynamic assigned one). >>>=20 >>> As always please report your bugs or experience with the new version to >>> this list. >>>=20 >>> Best regards, >>>=20 >>> -Stefan >>>=20 >>>> Hello mailing list followers, >>>>=20 >>>> this is the official release announcement for the first beta release >>>> of >>>> the new Guardian 2.0 approach. >>>>=20 >>>>=20 >>>> - What are the differences to the current version of guardian >>>> (legacy) >>>> and the first approach of guardian 2.0? >>>>=20 >>>> 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. >>>>=20 >>>> 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. >>>>=20 >>>> 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.=20 >>>>=20 >>>> 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. >>>>=20 >>>> 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". >>>>=20 >>>> 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. >>>>=20 >>>>=20 >>>> - How to join testing? >>>>=20 >>>> To get part of the testing team, simple navigate to http://people.ipf >>>> ir >>>> 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. >>>>=20 >>>> Put the downloaded file on your IPFire test system and extract the >>>> package by using "tar -xvf guardian-2.0-002..tar.gz -C /". >>>>=20 >>>> The final installation step would be to regenerate the language cache >>>> by executing "update-lang-cache" on the console. >>>>=20 >>>> 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. >>>>=20 >>>> Documentation can be found on the IPFire wiki: http://wiki.ipfire.org >>>> /e >>>> n/addons/guardian/start#the_guardian_20_addon >>>>=20 >>>>=20 >>>> - Where to post bugs reports or provide feedback? >>>>=20 >>>> If you find any bugs, please report them as usual on the IPFire >>>> bugtracker, which can be found at https://bugzilla.ipfire.org. >>>>=20 >>>> To provide feedback or to join a discussion, please send your mails >>>> to >>>> "development(a)lists.ipfire.org" (Please register first at http://lists >>>> .i >>>> pfire.org if not yet done). >>>>=20 >>>> The source code can be found at http://git.ipfire.org/?p=3Dpeople/steve >>>> e/ >>>> guardian.git;a=3Dsummary >>>>=20 >>>>=20 >>>> Happy testing, >>>>=20 >>>> -Stefan >>>>=20 >>>=20 >>=20 >=20 >=20 --===============0784772504382676909==--