Menu
▾
▴
[IPCop-devel] Fwd: Feature request [michael@rasmussen.cc]
|
From: Michael R. <mi...@mi...> - 2005-11-30 00:14:23
|
Sorry, wrong sender address:-) On 2005-11-30 01:09:38, Michael Rasmussen wrote: Hi all, Was it possible to add port knocking as a feature to IPCop? Motivation: These days especially ssh is a target for port scanning and =20 therefore it could be a great feature to add to IPCop. Was it possible to add the feature of been able to black list on an IP =20 level in IPCop? Both static and dynamic. Dynamic could be implemented =20 this way: The user specifies which port number(s) should be handled by =20 black listing and how many times a given IP are allowed to =20 unsuccesfully connect before it is automatically added to the =20 blacklist. This would also require an extra GUI under log where the =20 user could maintain the blacklist. This would require an extra rule in =20 iptables. --=20 Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael <at> rasmussen <dot> cc http://keyserver.veridis.com:11371/pks/lookup?op=3Dget&search=3D0xD3C9A00E mir <at> datanom <dot> net http://keyserver.veridis.com:11371/pks/lookup?op=3Dget&search=3D0xE501F51C mir <at> miras <dot> org http://keyserver.veridis.com:11371/pks/lookup?op=3Dget&search=3D0xE3E80917 -------------------------------------------------------------- BOFH excuse #268: Neutrino overload on the nameserver --=20 Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael <at> rasmussen <dot> cc http://keyserver.veridis.com:11371/pks/lookup?op=3Dget&search=3D0xD3C9A00E mir <at> datanom <dot> net http://keyserver.veridis.com:11371/pks/lookup?op=3Dget&search=3D0xE501F51C mir <at> miras <dot> org http://keyserver.veridis.com:11371/pks/lookup?op=3Dget&search=3D0xE3E80917 -------------------------------------------------------------- Darth Vader: I sense something. A presence I've not felt since... |