On 4/8/23 04:56, Mel Pilgrim wrote:
Can anyone suggest something equivalent in the port tree?
Have a look at fail2ban. It's design intent is monitoring running
services, but really it's just a set of log file regex filters. Anything
that logs network activity can feed it.
Hello and thanks
On 4/8/23 12:47 AM, Andrea Venturoli wrote:
On 4/8/23 04:56, Mel Pilgrim wrote:
Can anyone suggest something equivalent in the port tree?
Have a look at fail2ban. It's design intent is monitoring running
services, but really it's just a set of log file regex filters.
Anything that logs n
> On Apr 8, 2023, at 3:55 PM, Pete Wright wrote:
>
>
> On 4/8/23 12:47 AM, Andrea Venturoli wrote:
>> On 4/8/23 04:56, Mel Pilgrim wrote:
>>
Can anyone suggest something equivalent in the port tree?
>>>
>>> Have a look at fail2ban. It's design intent is monitoring running
>>> services
On 4/8/23 15:55, Pete Wright wrote:
would blacklistd(8) meet your requirements?
I guess not.
From the man:
blacklistd is a daemon similar to syslogd(8) that listens to sockets at
paths specified in the sockpathsfile for notifications from other daemons
The purpose of portsentry is
On 4/8/23 16:40, Helge Oldach wrote:
I wonder why that would provide anything useful though.
Main reason is to react to port scans or swiping attempts at well-known
service.
I.e. Someone (or some bot) connect to port 22, 25, 110, etc... when
there's no such service available and he/she/it ge
Christian Weisgerber:
> I just upgrade shells/yash, whose distfile is hosted on OSDN.
> I had to put the full URL into MASTER_SITES, because I can't figure
> out how to use the OSDN shortcut to fetch this:
Actually, the download page also offers a "simplified release file
URL", whose format match
On 2023-04-08 0:47, Andrea Venturoli wrote:
On 4/8/23 04:56, Mel Pilgrim wrote:
Can anyone suggest something equivalent in the port tree?
Have a look at fail2ban. It's design intent is monitoring running
services, but really it's just a set of log file regex filters. Anything
that logs networ
