| 1. | | XSS Twitter in minutes; Why you shouldn't store important data with 37signals (mastenbrook.net) |
| 156 points by antonovka on Sept 4, 2009 | 60 comments |
|
| 2. | | Get Less Done: Stop Being Productive and Enjoy Yourself (zenhabits.net) |
| 104 points by onreact-com on Sept 4, 2009 | 35 comments |
|
| 3. | | Joe Stump: Why I switched from PHP to Python (joestump.net) |
| 92 points by dannyr on Sept 4, 2009 | 95 comments |
|
| 4. | | Inventing Demand (startupblog.wordpress.com) |
| 88 points by tomhoward on Sept 4, 2009 | 32 comments |
|
| 5. | | Snakes on the Web (jacobian.org) |
| 87 points by arthurk on Sept 4, 2009 | 15 comments |
|
| 6. | | Smule: I am T-Pain (smule.com) |
| 79 points by ashishk on Sept 4, 2009 | 28 comments |
|
| 7. | | A Javascript date library (datejs.com) |
| 71 points by mcxx on Sept 4, 2009 | 31 comments |
|
| 8. | | Ask HN: 3 Ideas (with slides) for YC W10 - What do you think? (ycombinator-w10-cofounder-search.tumblr....) |
| 64 points by YCW10 on Sept 4, 2009 | 35 comments |
|
| 9. | | Loopt to work in the background on iPhone via deal with AT&T (businessinsider.com) |
| 62 points by fromedome on Sept 4, 2009 | 60 comments |
|
| |
|
|
| 11. | | Spreadsheet of every TED talk as of 9/2/2009 (boingboing.net) |
| 63 points by fogus on Sept 4, 2009 | 15 comments |
|
| 12. | | Revisiting PG's New Reality, 7 Months Later: Ticketstumbler vs. Fansnap (compete.com) |
| 61 points by Mystalic on Sept 4, 2009 | 36 comments |
|
| 13. | | Complexity is insecurity (daemonology.net) |
| 58 points by cperciva on Sept 4, 2009 | 15 comments |
|
| |
|
|
| |
|
|
| 16. | | Men lose their minds speaking to pretty women (telegraph.co.uk) |
| 55 points by timr on Sept 4, 2009 | 52 comments |
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| 23. | | Young Workers in Free Fall: 1/3 Under 35 Live with Parents (alternet.org) |
| 48 points by edw519 on Sept 4, 2009 | 75 comments |
|
| 24. | | Hacking goes squishy (economist.com) |
| 45 points by fauigerzigerk on Sept 4, 2009 | 37 comments |
|
| |
|
|
| 26. | | Fighting terrorism the Silicon Valley Way [video] (wsj.com) |
| 45 points by rantfoil on Sept 4, 2009 | 13 comments |
|
| 27. | | Why AI is a dangerous dream - interview with Noel Sharkey (newscientist.com) |
| 40 points by limist on Sept 4, 2009 | 77 comments |
|
| 28. | | Hidden messages in NES games' code (magweasel.com) |
| 40 points by amelim on Sept 4, 2009 | 9 comments |
|
| 29. | | The Companies Headhunters Avoid (businessweek.com) |
| 40 points by cwan on Sept 4, 2009 | 24 comments |
|
| |
|
|
|
| More |
This is hard to defend, guys.
It is literally the-simplest-thing-not-to-fuck-up. Nobody's asking you not to have security vulnerabilities. In fact: nobody's even asking you to fix vulnerabilities. We just need a reliable way to communicate with you about them.
If you're selling accounts on a web app, you need:
* A security page * With a PGP key * And an email contact * of someone who will write back * who knows what a security vulnerability is * and who will write back quickly.
That's it. Do that, and you're not a punch line. If someone dumps zero-day about you onto Twitter, you're already two steps ahead in the PR war, because you had a reasonable process, and the researcher ignored it.
Bonus points --- things that are trivial to do, but that nobody's even asking you to do:
* You can assign special issue numbers to vulnerabilities, to make the researcher feel like an XSS disclosure isn't the same thing as a bug in your online help.
* You can thank researchers privately, and let them know that you'd really like them to keep disclosing thing to you --- you could even give them (wait for it) a phone number.
* You can do what every vendor with a real security team does, and keep a public web page thanking people who have discreetly disclosed vulnerabilities to you.