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?
Digital Man wrote to Patch <=-
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.
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 think a temporary ban would be good, if possible, so if you do happen to lock yourself out, you just have to wait an hour or however long the ban is for, then try again. Also stops innocent people being locked out, because they just inherited a blacklisted IP. The aim would be to stop the scripts hammering away, while not overly inconveniencing innocent users.
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?
Patch wrote to Vk3jed <=-
Maybe have a way to make a temporary ban into a permanent one? So that you can get yourself back into your system without the bots or
potential hackers?
A lot of bots run on hijacked machines, which are often on dynamic IPs, so permanent bans aren't helpful here either. If the machine is on the same IP and still infected, it will simply trigger a new ban.
Patch wrote to Vk3jed <=-
Re: Re: Suggestion for SynchroNet
By: Vk3jed to Patch on Tue May 10 2016 10:03 pm
A lot of bots run on hijacked machines, which are often on dynamic IPs, so permanent bans aren't helpful here either. If the machine is on the same IP and still infected, it will simply trigger a new ban.
A very good point. So how do we out-smart the hijacked machines?
Temp ban to the whole subset?
If the bot doesn't receive a reply, it should move on. How can we make the bot believe that there's nothing for it to communicate with and
move on to someone else?
If the bot doesn't receive a reply, it should move on. How can we make the bot believe that there's nothing for it to communicate with and move on to someone else?
Well, a temporary ban should be enough. If it's still banging away at you an hour later, another temporary ban will be placed on it.
Well, a temporary ban should be enough. If it's still banging away at you an hour later, another temporary ban will be placed on it.
I likes it ...
Just something that stops bots or physical people from scanning for open IP ports (ex. war dialing) to see what they can get into.
Patch wrote to Vk3jed <=-
I likes it ...
Just something that stops bots or physical people from scanning for
open IP ports (ex. war dialing) to see what they can get into.
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?
... the issue where folks try to log ... using the name 'root'.
Sysop: | Tandy |
---|---|
Location: | New York, USA |
Users: | 15 |
Nodes: | 13 (0 / 13) |
Uptime: | 15:17:03 |
Calls: | 335 |
Messages: | 112,960 |