I publish open source tools for free. If you find my tools useful, please contribute to keeping them free: http://paypal.me/eam :-)
I spend my free time auditing code, publishing FOSS security tools, and tracking down accidentally exposed credentials. This helps keep a small corner of the Internet safe. Support my efforts by backing me via Patreon => https://www.patreon.com/user?u=16402577
1. Email company to responsibly disclose leaked customer API keys.
2. We don't have a disclosure process. No bounty. We'll let you know if that changes.
4. Email company to disclose more leaked keys. Also ask on bounty updates.
5. Thanks, but because you didn't fill out this other form, no bounty.
6. Point out they never disclosed the disclosure form.
7. "Oops. Too bad."
This is why responsible disclosure sucks...
Who forgot to pay Portland's heating bill? Sheesh! #pdxtst
Oh that's rich.
Just got a spam intercept of a message where my addy was in both the from and to fields, but was sent through another popped server (looks like an elementary school).
"This account has been hacked! I send you an email from YOUR hacked account!"
Kind of hilarious ... but also sad because I know a lot of people would fall for this nonsense.
WP Session Manager v4.1.0 is tagged and released. Fixes a couple of database race conditions, adds a cron to auto-clean up sessions under some more conservative configurations, and aborts early if running PHP <7.1
Want WP Session Manager to work on PHP 5.6. I'll do it, but only if the community pays for the time the extra support takes.
Contribute here => https://ttmm.io/wp-session-manager-support/