More actions
- 19:22, 26 July 2024 Setting Up Libmodsecurity3, Nginx Connector, & OWASP Ruleset on Nginx (hist | edit) [10,300 bytes] Admin (talk | contribs) (Created page with "= Setting Up Libmodsecurity3, Nginx Connector, & OWASP Ruleset on Nginx = thumb|none|alt=Logos|Logos == Background Info == Okay so tldr the modsecurity project recently back in January of 2024 switched hands from Trustwave SpiderLabs to the OWASP Foundation. [https://coreruleset.org/20240115/welcome-the-newest-addition-to-the-owasp-family-modsecurity/ More info here]. This transfer of stewardship means continued development of [https://github.c...")
- 19:52, 17 July 2024 Apache2 Mod Security v2.9.7 Compilation Instructions (hist | edit) [2,438 bytes] Admin (talk | contribs) (Created page with "== Overview == Going to be compiling <code>mod_security2</code> (v2.9.7) for Apache2 on Ubuntu 22.04. This module is pretty straight forward to compile. However, there are some dependencies. <pre>sudo apt install apache2-dev gcc libxml2 libxml2-dev libpcre3-dev</pre> Fetch the tarball from their github releases page. https://github.com/owasp-modsecurity/ModSecurity/releases/tag/v2.9.7 <pre>sudo su cd /opt wget https://github.com/owasp-modsecurity/ModSecurity/releases...")
- 21:08, 18 May 2024 Using Iperf3 for Speed Testing (hist | edit) [1,931 bytes] Admin (talk | contribs) (Created page with "Just found out about a cool little utility called <code>iperf3</code> for testing upload/download speeds between two hosts. On the server make sure to open the testing port on your firewall. Then run the following iperf3 command to start the server in your terminal. iperf3 -s -p 4000 I'm running it on port 4000. Then from the client machine you can run the following to test upload speeds. iperf3 -c SERVER_IP -p 4000 -t 10 If you stick a <code>-R</code> on there t...")
- 17:31, 17 May 2024 Keeping Sensitive Data Out of Your Shells History File (hist | edit) [1,469 bytes] Admin (talk | contribs) (Created page with "We've all been there before. <code>some_command</code> takes a flag for --password or --api_key. The lazy thing to do is just supply the password as part of your command. But there are two big downsides of doing that. First, it goes into your shell's history file and if you just leave it there someone could find it and use it to steal your bits! Second it goes into the process list and is potentially visible to other users on the system who are just viewing the process t...")
- 01:09, 30 April 2024 Do cmd X times without a forloop (hist | edit) [176 bytes] Admin (talk | contribs) (Created page with "Say you're in a weird shell and you don't know how to do a forloop. No worries! You can use seq | xargs to run some command any number of times. seq 5 | xargs -I {} echo fart")
