How noorqureshi/kali-linux-cheatsheet works
Project Type and Purpose
• This is an informational, reference project—a Penetration Testing Cheat Sheet.
• Its purpose is to serve as a quick reference guide outlining commands, techniques, and methods for various penetration testing activities, including recon, exploitation, brute forcing, password cracking, and more.
File Structure
• The file tree is minimal (just the README.md file), meaning that all information is consolidated into one document.
• Since there’s one “source” file, the architectural focus is on the content structure within the README rather than a software module hierarchy.
README for Insights
• The content is divided into clearly marked sections such as “Recon and Enumeration”, “Python Local Web Server”, “Mounting File Shares”, and many others.
• The cheat sheet encompasses a wide range of topics. Groupings include network scanning (NMAP, SMB Enumeration, etc.), payload deployment, password operations (wordlists, brute forcing, cracking), exploit research, Metasploit modules, networking details (IPv4, ASCII tables), and Cisco IOS commands.
• These groups can be seen as “components” in the overall architecture of the cheat sheet.
• Main Components to Include:
◦ Overall Title/Node: “Penetration Testing Cheat Sheet”
• Recon and Enumeration (with nodes for NMAP Commands, SMB Enumeration, Other Host Discovery Methods)
• Python Local Web Server
• Mounting File Shares
• Basic FingerPrinting
• SNMP Enumeration
• DNS Related Techniques (DNS Zone Transfers, DNSRecon)
• HTTP/HTTPS Webserver Enumeration
• Packet Inspection
• Username Enumeration (with further split into SMB and SNMP sections)
• Password Tools (Wordlists, Hydra, Password Cracking with John The Ripper & Hashcat)
• Exploit Research and Compiling Exploits (including SUID Binary and TTY Shells)
• Metasploit (payloads, modules, post-exploit modules)
• Networking Details (TTL Fingerprinting, IPv4 details)
• Additional References (ASCII Table, Cisco IOS Commands, Cryptography, SQLMap Examples)
• Relationships and Interactions:
◦ Identify “flows” where applicable: for example, starting at Recon, then moving through gaining access (payload delivery, brute forcing) and finally privilege escalation (SUID binaries, TTY Shells).
• Architectural Patterns/Design Principles:
• Relevant Technologies:
◦ Commands and tools are based on technologies like Nmap, SMB tools, Python-based web servers, Hydra, John The Ripper, Hashcat, and Metasploit. Although they don’t constitute a “software stack,” they are key to understanding the flow in a pentesting scenario.