> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/useful-resources.md). # Useful Resources Useful offensive security resources organized into bug bounty case studies, forensics helpers, exploit development practice, reporting material, certification preparation, and workstation setup notes. Practical reference material that supports offensive security work but does not need a full methodology section. Use this page as the master map for bug bounty case studies, small helpers, exploit development labs, report writing, certification notes, and workstation setup references. ## Resource Areas

:bug:

Bug Bounty

Responsible disclosure case studies, real-world PoCs, impact analysis, remediation notes, and bug bounty reporting workflows.Bug Bounty

:fingerprint:

Forensics

Forensics helper notes for steganography, Steghide, image recovery, and Depix workflows used in CTFs and offensive security labs.Forensics

:microchip:

Exploit Development

Exploit development practice notes for Linux and Windows buffer overflow labs, offsets, bad characters, shellcode, and payload delivery.Exploit Development

:file-lines:

Reporting

Reporting resources for LaTeX pentest reports, professional deliverables, evidence structure, and example write-up material.Reporting

:graduation-cap:

Certifications

Certification preparation resources for practical penetration testing study, exam strategy, and eJPT notes.Certifications

:desktop:

Arch Linux Hacker Setup With BSPWM

Arch Linux BSPWM workstation setup notes for installing and validating gh0stzk dotfiles, themes, Rofi, Polybar, ZSH, and Neovim.Arch Linux Hacker Setup With BSPWM
### Workflow 1. Use bug bounty notes for real findings, responsible disclosure, PoCs, impact, and remediation. 2. Use forensics helpers for media files, hidden data, and visual recovery tasks. 3. Use exploit development notes for memory corruption and buffer overflow labs. 4. Use reporting resources when structuring evidence, screenshots, and final deliverables. 5. Use certification notes as study support alongside hands-on practice. 6. Use workstation setup notes when building a clean Linux lab desktop. ## Navigation Guide * Use [Bug Bounty](/useful-resources/bug-bounty.md) for real-world responsible disclosure case studies. * Use [Forensics](/useful-resources/forensics.md) for Steghide and Depix workflows. * Use [Exploit Development](/useful-resources/exploit-development.md) for Linux and Windows buffer overflow practice. * Use [Reporting](/useful-resources/reporting.md) for LaTeX report material and examples. * Use [Certifications](/useful-resources/certifications.md) for exam preparation notes. * Use [Arch Linux Hacker Setup With BSPWM](/useful-resources/gh0stzk-bspwm-dotfiles.md) for Arch-based BSPWM workstation setup. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://hacking-notes.jord4n.pro/useful-resources.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.