I've noticed and I know we've all talked about the issue where folks try to log onto our boards using the name 'root'.
I also know that there's a way to add IP addresses to a .can file to block the IP address.
Why can't we combine them as a 'feature' to SynchrNet?
How hard would it be to add an optional function so that if someone makes a successful connection and uses pre-defined banned user names like 'root' or the ilk, which allows a bogus connection that says something 'nice' to the connection, places the IP address in the banned file and terminates the connection.
Anyone?
Doesn't sound like it would be too hard. I sometimes accidentally try to login to my own board as "root" though and wouldn't want to have my own IP banned! You probably want something a little less aggressive.
I've noticed and I know we've all talked about the issue where folks try to onto our boards using the name 'root'.
I also know that there's a way to add IP addresses to a .can file to block t IP address.
Why can't we combine them as a 'feature' to SynchrNet?
How hard would it be to add an optional function so that if someone makes a successful connection and uses pre-defined banned user names like 'root' or ilk, which allows a bogus connection that says something 'nice' to the connection, places the IP address in the banned file and terminates the connection.
Anyone?
How hard would it be to add an optional function so that if someone makes
a successful connection and uses pre-defined banned user names like 'root' or the ilk, which allows a bogus connection that says something 'nice' to the connection, places the IP address in the banned file and terminates
the connection.
Anyone?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 58:22:55 |
Calls: | 6,652 |
Calls today: | 4 |
Files: | 12,200 |
Messages: | 5,331,136 |