Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Corporate PR lessons from this post:

- Push security breach details down so fewer people read them. Nothing until line 11. Or line 13 if you count the TLDR.

- Litter your text with understatements. After publicly exposing keys, you replace them "out of an abundance of caution" to replace them.

And yet this is one of the best security breach posts I've seen in a while. When will companies start to respect developers?



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: