[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dropbear
Subject:    Re: restrict access
From:       Sebastian Gottschall <s.gottschall () dd-wrt ! com>
Date:       2021-05-20 14:41:32
Message-ID: b0a0cb46-6991-1c84-613f-06e7aa83e14d () dd-wrt ! com
[Download RAW message or body]

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 <dropbear-bounces@ucc.asn.au> im Auftrag von Sebastian Gottschall \
>                 <s.gottschall@dd-wrt.com>
> 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


[prev in list] [next in list] [prev in thread] [next in thread]