Re: Hacker log

2016-10-22 Thread li...@lazygranch.com
On Sat, 22 Oct 2016 17:40:56 -0400 "itpp2012" wrote: > The idea is nice but pointless, if you maintain this list over 6 > months you most likely will end up blocking just about everyone. > > Stick to common sense with your config, lock down nginx and the > backends, define proper flood and overf

Re: Hacker log

2016-10-22 Thread itpp2012
The idea is nice but pointless, if you maintain this list over 6 months you most likely will end up blocking just about everyone. Stick to common sense with your config, lock down nginx and the backends, define proper flood and overflow settings for nginx to deal with, anything beyond the scope of

Hacker log

2016-10-22 Thread li...@lazygranch.com
http://pastebin.com/7W0uDrLa If you need an extensive list of hacker requests (over 200), I put this log entry on pastebin. As mentioned at the top of the pastebin, the hacker used my IP address directly rather than my doman name. I have a "map" that detects typical hacker activity. Perhaps in m