>>/1111/
Self defense primarily.
Read these threads the answer is in here:
https://archive.is/INR3l
https://archive.is/bpQXa
Anonymous 02/14/2016 (Sun) 00:10:59 [Preview] No. 1726
About the developer:
I will remain anonymous as best I can.
I am not a professional computer scientist or programmer.
I have other commitments and can't maintain a continuous development cycle, but will work on this project sporadically as I have ideas or as issues emerge.Help and assistance on ideas are welcome. Critique and criticism of my tools are also welcome. Positive and negative reviews of experiences using endwall endset and endtools are also welcome.Point out any bugs that you find in the code and or errors in logic or in style or implementation that you find in the script and I may modify it in a release upon review.
Anonymous 02/13/2016 (Sat) 06:51:33 [Preview] No. 1693
>>/1687/
1)My hope was to get some help with internet security by starting a thread asking for contributions of techniques and ideas. So far that's worked out pretty well. that ipsets thing has solved a major problem my server was running into. I'm glad I got that tip from here. Thanks >>/1652/ good work!
2) I think every newb should run this as standard fair. Every new linux user should run this endwall. I don't care what >>/1652/ is implying. This script stands between me and the ridiculous daily hack attempts against my tiny little mail server / website. I run this script on all my laptops (modified) all my network machines in my house, and I want everyone in the world to use this or the ideas in it as the defacto standard starting point. I think my script works. I think this script endwall.sh should be run after install on any/every linux machine period.
3) I found several problems in my personal version of this script while reading and fixing endwall.sh so that was worth the exercise in its self.