I wasn't sure if it was ready to be in the repo or not. So, just let me know.
and now, how looks?
I wasn't sure if it was ready to be in the repo or not. So, just let me know.
and now, how looks?
Since I didn't get a response, I just put it in the testing repo.
He haven't testing it yet ...
He haven't testing it yet ...
While I don't use the plugin, I did test it and found a small bug in the bindListeners code. 1.3.1 is in the repo now.
thanks @ryecoaaron
on the instalation i have warnings:
Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
fail2ban whois
Suggested packages:
python-gamin
Recommended packages:
python-pyinotify
The following NEW packages will be installed:
fail2ban openmediavault-fail2ban whois
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 250 kB of archives.
After this operation, 857 kB of additional disk space will be used.
Get:1 http://ftp.de.debian.org/debian/ jessie/main whois amd64 5.2.7 [65.8 kB]
Get:2 http://ftp.de.debian.org/debian/ jessie/main fail2ban all 0.8.13-1 [165 kB]
Get:3 https://dl.bintray.com/openmediavault-plugin-developers/erasmus-testing/ jessie/main openmediavault-fail2ban all 1.3.0 [18.8 kB]
Fetched 250 kB in 0s (265 kB/s)
Selecting previously unselected package whois.
(Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 53356 files and directories currently installed.)
Preparing to unpack .../archives/whois_5.2.7_amd64.deb ...
Unpacking whois (5.2.7) ...
Selecting previously unselected package fail2ban.
Preparing to unpack .../fail2ban_0.8.13-1_all.deb ...
Unpacking fail2ban (0.8.13-1) ...
Selecting previously unselected package openmediavault-fail2ban.
Preparing to unpack .../openmediavault-fail2ban_1.3.0_all.deb ...
Unpacking openmediavault-fail2ban (1.3.0) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for systemd (215-17+deb8u5) ...
Processing triggers for openmediavault (3.0.40) ...
Restarting engine daemon ...
Setting up whois (5.2.7) ...
Setting up fail2ban (0.8.13-1) ...
Setting up openmediavault-fail2ban (1.3.0) ...
WARNING: The function 'omv_config_add_element' is deprecated.
WARNING: The function 'omv_config_add_element' is deprecated.
WARNING: The function 'omv_config_add_element' is deprecated.
WARNING: The function 'omv_config_add_element' is deprecated.
WARNING: The function 'omv_config_add_element' is deprecated.
WARNING: The function 'omv_config_add_element' is deprecated.
WARNING: The function 'omv_config_add_element' is deprecated.
WARNING: The function 'omv_config_add_element' is deprecated.
WARNING: The function 'omv_config_add_element' is deprecated.
WARNING: The function 'omv_config_add_element' is deprecated.
WARNING: The function 'omv_config_add_element' is deprecated.
WARNING: The function 'omv_config_add_element' is deprecated.
WARNING: The function 'omv_config_add_element' is deprecated.
WARNING: The function 'omv_config_add_element' is deprecated.
WARNING: The function 'omv_config_add_element' is deprecated.
WARNING: The function 'omv_config_add_element' is deprecated.
Processing triggers for systemd (215-17+deb8u5) ...
Processing triggers for openmediavault (3.0.40) ...
Updating locale files ...
Updating file permissions ...
Purging internal cache ...
Restarting engine daemon ...
Creating index of upgradeable packages ...
Creating index of openmediavault plugins ...
Fertig ...
Alles anzeigen
and on the first i del the apache and owncloud jails
They are just warnings (just released with 3.0.40) and easy to fix. No worries.
I make a fix but i don't know why the commit 3ef17e5c95863c2cd983b0e48c296ae78f594749 is under you fix ...
Your clock on the committing computer may have been wrong? Not sure.
@ryecoaaron My vm wasn't at the good time ... i'am sorry, you can correct the problem ?
@happyreacer What's the problem ? any error log ?
i'am sorry, you can correct the problem ?
I think it is fine. Doesn't really matter if it is out of order.
Hi,
Update: it's working on Debian Jessie.
Anybody in here have a working filter for Emby?
Mine isn't working.
Log path: /media/54bf67db-da31-4c50-bb3c-27140944b223/emby/logs/server-*.txt
# Fail2Ban filter for emby
#
[INCLUDES]
# Read common prefixes. If any customizations available -- read them from
# common.local
before = common.conf
[Definition]
_daemon = emby-server
failregex = Info HttpServer: HTTP Response 401 to <HOST>.*authenticatebyname
Info HttpServer: HTTP Response 500 to <HOST>.*mediabrowser/Users/None
ignoreregex =
# DEV Notes:
#
# Matching on http 401 with a trailing url including 'authenticatebyname' to catch incorrect passwords
# Matching on http 500 with a trailing url including 'mediabrowser/Users/None' to catch incorrect usernames
#
Alles anzeigen
Yes, If you want. You going to have the last feature !!
Ok, but will the fail2ban GUI be there in OMV ?
Can I remove the fail2ban folder after the installation?
drwxrwxr-x 8 root root 660 Jul 31 2015 .
drwxrwxrwt 10 root root 260 Nov 21 21:14 ..
drwxrwxr-x 2 root root 120 Jul 31 2015 bin
-rw-rw-r-- 1 root root 62201 Jul 31 2015 ChangeLog
drwxrwxr-x 4 root root 220 Jul 31 2015 config
-rw-rw-r-- 1 root root 1107 Jul 31 2015 CONTRIBUTING.md
-rw-rw-r-- 1 root root 19296 Jul 31 2015 COPYING
-rw-rw-r-- 1 root root 130 Jul 31 2015 .coveragerc
-rw-rw-r-- 1 root root 8584 Jul 31 2015 DEVELOP
drwxrwxr-x 2 root root 1020 Jul 31 2015 doc
drwxrwxr-x 5 root root 200 Jul 31 2015 fail2ban
-rwxrwxr-x 1 root root 261 Jul 31 2015 fail2ban-2to3
-rwxrwxr-x 1 root root 399 Jul 31 2015 fail2ban-testcases-all
-rwxrwxr-x 1 root root 399 Jul 31 2015 fail2ban-testcases-all-python3
drwxrwxr-x 6 root root 420 Jul 31 2015 files
-rw-rw-r-- 1 root root 19278 Jul 31 2015 FILTERS
-rw-rw-r-- 1 root root 86 Jul 31 2015 .gitignore
-rwxrwxr-x 1 root root 69 Jul 31 2015 kill-server
drwxrwxr-x 2 root root 260 Jul 31 2015 man
-rw-rw-r-- 1 root root 12312 Jul 31 2015 MANIFEST
-rw-rw-r-- 1 root root 199 Jul 31 2015 MANIFEST.in
-rw-rw-r-- 1 root root 371 Jul 31 2015 .project
-rw-rw-r-- 1 root root 431 Jul 31 2015 .pydevproject
-rw-rw-r-- 1 root root 1311 Jul 31 2015 .pylintrc
-rw-rw-r-- 1 root root 3874 Jul 31 2015 README.md
-rw-rw-r-- 1 root root 4189 Jul 31 2015 README.Solaris
-rw-rw-r-- 1 root root 6417 Jul 31 2015 RELEASE
-rw-rw-r-- 1 root root 244 Jul 31 2015 setup.cfg
-rwxrwxr-x 1 root root 5684 Jul 31 2015 setup.py
-rw-rw-r-- 1 root root 2114 Jul 31 2015 THANKS
-rw-rw-r-- 1 root root 908 Jul 31 2015 TODO
-rw-rw-r-- 1 root root 2222 Jul 31 2015 .travis.yml
-rw-rw-r-- 1 root root 963 Jul 31 2015 Vagrantfile
Alles anzeigen
What is the most OMV-friendly way to install fail2ban currently? It's not showing up in the plugins list.
Thanks
What is the most OMV-friendly way to install fail2ban currently? It's not showing up in the plugins list.
Do you have the omv-extras testing repo enabled?
Yes, I do, and have OpenVPN installed, for example.
Yes, I do, and have OpenVPN installed, for example.
The openvpn plugin is in the regular repo not the testing repo though. What is the output of: apt-cache policy openmediavault-fail2ban
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!