non-technical bugbounty tips
Summary
Joseph Thacker's non-technical bug bounty tips: write verbose and clear reports, be assertive but respectful when a valid bug is closed in error, and default to sharing stuck findings with 2-3 peers instead of giving up.
- Published
- Collected
Skip to content