Security
Last updated 10 November 2026.
Reporting a vulnerability
If you find a security issue on this site, please tell me before telling anyone else:info@leslielangendorf.tech. Say what you found, how to reproduce it, and your contact details if you want a reply. I acknowledge every genuine report, confirm whether it reproduces, fix it, and let you know once it is fixed. There is no bug bounty program; credit in a note on this page, if you want it, is the only reward on offer today. See /.well-known/security.txt for the machine readable version of this.
What this site actually does
- Content on this site can only ever be changed through my own authenticated connection; there is no public write path anywhere, enforced at the database level on every table.
- Every response from this site carries a Content Security Policy and the other standard security headers.
- Installers are hosted as release files on GitHub; pressing a download button sends you there to fetch the file. Where I publish a checksum for a file, it appears next to the download so you can compare it with the file you received.
- No visitor tracking cookie exists anywhere on this site, and the download counter stores only a one way hash of your IP address and browser, kept at most 7 days; see the cookie policy.
What this is not
This is a personal portfolio, not a bank or a hospital system. There is no guaranteed response time, but every genuine report will get a reply.