fail2ban

Commit Graph

Author	SHA1	Message	Date
Yaroslav Halchenko	638bb66523	BF: Use /var/run/fail2ban instead of /tmp for temp files in actions: see http://bugs.debian.org/544232 It should be robust since /var/run/fail2ban is guaranteed to exist to carry the socket file, and it will be owned by root (or some other dedicated fail2ban user) thus avoiding possibility for the exploit git-svn-id: https://fail2ban.svn.sourceforge.net/svnroot/fail2ban/branches/FAIL2BAN-0_8@767 a942ae1a-1317-0410-a47c-b1dcaea8d605	2011-03-23 20:35:56 +00:00
Cyril Jaquier	6cd56802bb	- Added actions to report abuse to ISP, DShield and myNetWatchman. Thanks to Russell Odom. git-svn-id: https://fail2ban.svn.sourceforge.net/svnroot/fail2ban/branches/FAIL2BAN-0_8@717 a942ae1a-1317-0410-a47c-b1dcaea8d605	2008-10-13 14:56:54 +00:00

Author

SHA1

Message

Date

Yaroslav Halchenko

638bb66523

BF: Use /var/run/fail2ban instead of /tmp for temp files in actions: see http://bugs.debian.org/544232

It should be robust since /var/run/fail2ban is guaranteed to exist to carry the
socket file, and it will be owned by root (or some other dedicated fail2ban
user) thus avoiding possibility for the exploit

git-svn-id: https://fail2ban.svn.sourceforge.net/svnroot/fail2ban/branches/FAIL2BAN-0_8@767 a942ae1a-1317-0410-a47c-b1dcaea8d605

2011-03-23 20:35:56 +00:00

Cyril Jaquier

6cd56802bb

- Added actions to report abuse to ISP, DShield and myNetWatchman. Thanks to Russell Odom.

git-svn-id: https://fail2ban.svn.sourceforge.net/svnroot/fail2ban/branches/FAIL2BAN-0_8@717 a942ae1a-1317-0410-a47c-b1dcaea8d605

2008-10-13 14:56:54 +00:00

2 Commits (dad91f7969871e737c616f47ba09b60cc3036764)