Hi all,
For anyone who missed my Inkscape presentation but wants to see it, I'm
giving it again at the monthly Phoenix (Arizona USA) LUG (PLUG) meeting
1/13/2022 at 7pm **Mountain Time** (Phoenix, Denver, and Salt Lake City
USA time).
You can see details at
Alessandro Vesely via Dng said on Wed, 12 Jan 2022 10:39:07 +0100
>On Wed 12/Jan/2022 01:27:45 +0100 Florian Zieboll via Dng wrote:
>> On Tue, 11 Jan 2022 18:52:10 -0500
>> william moss wrote:
>>
>>> Bash is taking the string in the double quotes as a single command;
>>> this is well
onefang wrote:
> My main problem with fail2ban is that it fails to ban. Or rather it does
> ban, for that one rule I wrote myself, but not for any of the built in
> rules, but then it releases the ban, even though I have told shorewall to
> ban that particular IP. So the IP ends up being
On 1/12/22 04:39, Alessandro Vesely via Dng wrote:
On Wed 12/Jan/2022 01:27:45 +0100 Florian Zieboll via Dng wrote:
On Tue, 11 Jan 2022 18:52:10 -0500
william moss wrote:
Bash is taking the string in the double quotes as a single command;
this is well documented. If either the command or
On Wed, 12 Jan 2022 10:39:07 +0100
Alessandro Vesely via Dng wrote:
> On Wed 12/Jan/2022 01:27:45 +0100 Florian Zieboll via Dng wrote:
> >
> > I am replying to the list to share the valid (tested) alternative.
> > Thanks a lot!
>
>
> Bash still considers a quoted command as such, for
A technique I learned is to use the "fail2ban-regex" command with a
log file sample containing actual traffic that you want banned.
E.g. for Apache logs from the shell prompt:
$ fail2ban-regex /path/to/apache/logs/access_log..??.??-??_??_??
/etc/fail2ban/filter.d/apache-404.conf
You'll
I've been using shorewall and fail2ban for a while now, but nftables is
soon replacing iptables, so it's time to consider some options.
Apparently fail2ban already supports nftables, but shorewall doesn't and
wont -
https://shorewall-users.narkive.com/aujuSpJ1/nftables-on-the-roadmap
My main
On Wed 12/Jan/2022 01:27:45 +0100 Florian Zieboll via Dng wrote:
On Tue, 11 Jan 2022 18:52:10 -0500
william moss wrote:
Bash is taking the string in the double quotes as a single command;
this is well documented. If either the command or parameters have
spaces, you will have to use eval.
