News for hackers. Stuff that matters.
Re:How I Discovered a Security Vulnerability in Twitter That... by tptacek on Thursday February 03, 2011 @11:30AM (#2175318)
You usually don't have to write headlines like "1.5M users compromised!" to get people to fix trivial web flaws. Also, before asking VC's and posting public Twitter messages and spending two days trying to track down a security contact, try mailing "security@" first; as you discovered, that sensible default generated an immediate response.

Edited out "not '96 anymore", the word "breathless", and my assessment of his effort to track down security@ as "hinky"; I wasn't happy with the tone of this comment in retrospect either.

Re:How I Discovered a Security Vulnerability in Twitter That... by ttol on Thursday February 03, 2011 @11:40AM (#2175374)
No, the security pages were put up after I talked to Bob. (Those are new pages and are about a week old. They were put up precisely because it wasn't easy for people to report security issues.). Also the headline wasn't written by me. Boston Innovation editors modified it. My original headline is on my website at waynechang.com. And yes, it was hard to get a hold of someone -- I spent two days. Emailing [email protected] was less obvious then, since emailing [email protected] sends back a form rejection letter (try it).
Re:How I Discovered a Security Vulnerability in Twitter That... by tptacek on Thursday February 03, 2011 @12:18PM (#2175539)
You're right. The headline on your site is "How I Discovered A Security Vulnerability In Twitter"; the "I found another security vulnerability that impacted 1-1.5 million Twitter accounts." copy is in your subhed. My mistake.
Re:How I Discovered a Security Vulnerability in Twitter That... by nbpoole on Thursday February 03, 2011 @11:36AM (#2175354)
http://twitter.com/about/security has been on their website for a little while now, but it's not so easy to find via Google (at least for me).
Re:How I Discovered a Security Vulnerability in Twitter That... by ttol on Thursday February 03, 2011 @11:41AM (#2175376)
Yea -- it's hard to find because the twitter.com/about/security page is about a week old. When google updates their indexes, it should be easier to find.
Re:How I Discovered a Security Vulnerability in Twitter That... by nbpoole on Thursday February 03, 2011 @11:47AM (#2175403)
My mistake: for some reason I thought it had been around for a little bit longer than that.