Security policy
If you've found a security problem with anything I run, I'd like to hear about it.
How to report
Email security@klercke.com. If the details are sensitive, encrypt your message to my PGP key. Please include what you found, how to reproduce it, and what you think the impact is.
In scope
- klercke.com and its subdomains
- The browser shell at klercke.com/shell/
- The SSH shell at
ssh klercke.com - The source code at github.com/klercke/website
- Any other project I host, especially if the source code is posted on my GitHub
Out of scope
- Services I use but don't run: Plausible, GitHub, my mail and hosting providers. Report those to their owners.
- Denial of service, load testing, or anything that degrades the site for others
- Social engineering, phishing, or physical attacks
- Scanner output with no demonstrated impact (missing headers, TLS or SSH algorithm preferences, version banners)
What to expect
This is a personal site run by one person, so there's no bug bounty. I'll acknowledge your report within a week and keep you updated while I work on it. I'd ask that you give me 90 days to fix it before you disclose it publicly, if you choose to do so. If it's fixed sooner, you can publish sooner. With your permission, I'll credit you in the hall of fame.
Safe harbor
If you act in good faith, stay within the scope above, don't access or keep other people's data, and give me a chance to fix the problem before you disclose it, I won't pursue or support legal action against you for your research.