AW: restrict access
Thx for the fast response, for the background: little system, far-far-away land, but some script-kiddie is filling the log ... so no iptables or other fancy stuff. Seems i have to change that, somehow. @matt: in case i get something working ... i am thinking about fnmatch and inet_ntoa would that be acceptable ? re, wh Von: Dropbear im Auftrag von Sebastian Gottschall Gesendet: Donnerstag, 20. Mai 2021 15:53 An: dropbear@ucc.asn.au Betreff: Re: restrict access isnt that a job for netfilter? Am 20.05.2021 um 15:23 schrieb Walter Harms: > Hello List, > actually i expected this would be a FAQ but i can not find an answer: > How can i restrict the hosts that are allowed to access the > dropbear server ? > > re, > wh
Re: restrict access
I've used successfully (well, at least I believe it's successful) sshblack ( http://www.pettingers.org/code/sshblack.html) to block those pesky robots through iptables. To get it to work correctly It's not as obvious as it seems... and there are some limitations, but once you are familiar with it, it does its job. (In particular, the main issue of sshblack is that if not set up correctly, its database and iptables goes out of sync after a reboot of the host and it essentially fails to block login attempts. email me directly for more details). Regards, Fabrizio On Thu, May 20, 2021 at 11:09 AM Sebastian Gottschall < s.gottsch...@dd-wrt.com> wrote: > what about a feature like blocking a client for N minutes if more than N > times of failed logins. its relativily easy to implement and lows down > brute force attacks > > Am 20.05.2021 um 16:44 schrieb Matt Johnston: > > On Thu, May 20, 2021 at 02:29:20PM +, Walter Harms wrote: > >> Thx for the fast response, > >> for the background: little system, far-far-away land, but some > script-kiddie is filling the log ... > >> so no iptables or other fancy stuff. Seems i have to change that, > somehow. > >> > >> @matt: > >> in case i get something working ... > >> i am thinking about fnmatch and inet_ntoa would that be acceptable ? > > I'm not really sure it's the job of Dropbear to be doing > > that filtering. Though I wonder if it might make sense to > > optionally not bother logging failed SSH auth attempts, > > given how many there are... > > > > Cheers, > > Matt > > >
Re: restrict access
what about a feature like blocking a client for N minutes if more than N times of failed logins. its relativily easy to implement and lows down brute force attacks Am 20.05.2021 um 16:44 schrieb Matt Johnston: On Thu, May 20, 2021 at 02:29:20PM +, Walter Harms wrote: Thx for the fast response, for the background: little system, far-far-away land, but some script-kiddie is filling the log ... so no iptables or other fancy stuff. Seems i have to change that, somehow. @matt: in case i get something working ... i am thinking about fnmatch and inet_ntoa would that be acceptable ? I'm not really sure it's the job of Dropbear to be doing that filtering. Though I wonder if it might make sense to optionally not bother logging failed SSH auth attempts, given how many there are... Cheers, Matt
Re: restrict access
On Thu, May 20, 2021 at 02:29:20PM +, Walter Harms wrote: > Thx for the fast response, > for the background: little system, far-far-away land, but some script-kiddie > is filling the log ... > so no iptables or other fancy stuff. Seems i have to change that, somehow. > > @matt: > in case i get something working ... > i am thinking about fnmatch and inet_ntoa would that be acceptable ? I'm not really sure it's the job of Dropbear to be doing that filtering. Though I wonder if it might make sense to optionally not bother logging failed SSH auth attempts, given how many there are... Cheers, Matt
Re: restrict access
even for little systems. i dont now if its about linux or something else, but even the smallest linux systems are comming with iptables at least. but if you have problems with brute force login attempts (we all have that), i can just suggest to use fail2ban. i use it to prevent the thousands of login attempts per day on my systems Am 20.05.2021 um 16:29 schrieb Walter Harms: Thx for the fast response, for the background: little system, far-far-away land, but some script-kiddie is filling the log ... so no iptables or other fancy stuff. Seems i have to change that, somehow. @matt: in case i get something working ... i am thinking about fnmatch and inet_ntoa would that be acceptable ? re, wh Von: Dropbear im Auftrag von Sebastian Gottschall Gesendet: Donnerstag, 20. Mai 2021 15:53 An: dropbear@ucc.asn.au Betreff: Re: restrict access isnt that a job for netfilter? Am 20.05.2021 um 15:23 schrieb Walter Harms: Hello List, actually i expected this would be a FAQ but i can not find an answer: How can i restrict the hosts that are allowed to access the dropbear server ? re, wh
Re: restrict access
isnt that a job for netfilter? Am 20.05.2021 um 15:23 schrieb Walter Harms: Hello List, actually i expected this would be a FAQ but i can not find an answer: How can i restrict the hosts that are allowed to access the dropbear server ? re, wh
Re: restrict access
Hi Walter, Dropbear doesn't have IP restrictions built in. You could use iptables/nftables, or tcpwrappers etc if you're running Dropbear in inetd mode. Cheers, Matt On Thu, May 20, 2021 at 01:23:28PM +, Walter Harms wrote: > Hello List, > actually i expected this would be a FAQ but i can not find an answer: > How can i restrict the hosts that are allowed to access the > dropbear server ? > > re, > wh
restrict access
Hello List, actually i expected this would be a FAQ but i can not find an answer: How can i restrict the hosts that are allowed to access the dropbear server ? re, wh
