On Tuesday, January 12, 2021 5:22:20 AM CET the...@sys-concept.com wrote: > On 1/11/21 9:15 PM, mad.scientist.at.la...@tutanota.com wrote: > > --"Fascism begins the moment a ruling class, fearing the people may use > > their political democracy to gain economic democracy, begins to destroy > > political democracy in order to retain its power of exploitation and > > special privilege." Tommy Douglas > [snip] > > >> I forgot to mention, my firewall doesn't have any capabilities to enter > >> any configuration in IP tables. Maybe I'll look for one that does. > > > > That would be the thing to do. You want everything logged, so you know > > what is happening. If you blocked the logging how would you know if they > > made progress. You want to know when people are trying to break in, and > > you want to know when their tactics change. Not logging it is like > > plugging your' ears and closing your' eyes while the battering ram is > > pounding your' door... > If I blocked the IP already, why would I want to log anything about that IP; > they will will be denied access regardless.
If you blocked the IP in the firewall, it shouldn't show in the log. Add iptables to the webserver and block that IP. Personally, I would block the whole range (45.93.201.0/24), which is either linked to Cyprus or Russia (according to whois) Any block in the apache-config might fail due to a bug or new configuration. -- Joost