Re:Analyzing the attacks on my website
by ringzero on Saturday February 08, 2020 @05:38PM
(#22279055)
You may have accidentally reinvented https://en.wikipedia.org/wiki/Fail2ban :)
[ Parent
| on HN ]
Re:Analyzing the attacks on my website
by JeremyMorgan on Saturday February 08, 2020 @06:07PM
(#22279245)
That wasn't really the point of the article, I'm showing how to gather data on where they came from. Blocking is completely optional, and not for everyone.
fail2ban is saving my bacon right now.
Re:Analyzing the attacks on my website
by ryanlol on Saturday February 08, 2020 @09:39PM
(#22280032)
From what? Generally fail2ban only exposes unnecessary attack surface while providing zero benefit.
Re:Analyzing the attacks on my website
by omgwtfbyobbq on Saturday February 08, 2020 @10:16PM
(#22280176)
How does fail2ban expose attack surface?
It's code running on partially attacker-controlled inputs. It several times had vulnerabilities that allowed an attacker to trigger blocks for arbitrary IPs.
I remember there's a privEsc on old versions of fail2ban.
Re:Analyzing the attacks on my website
by omgwtfbyobbq on Monday February 10, 2020 @07:27PM
(#22294888)
Do you remember roughly when the privEsc was?
https://www.cvedetails.com/vulnerability-list/vendor_id-5567...