3 ms·
Only in the white hat sense of security research. This isn't anything that existing, legitimate security companies don't do routinely. He contacted them befor
by ajross 15y ago
Only in the white hat sense of security research. This isn't anything that existing, legitimate security companies don't do routinely. He contacted them before publication, and while the timeline isn't clear it seems that the fix was live before the article was.
This is good behavior, not bad.
- tptacek 15y agoIf the WSJ did anything more than what Kickstarter can reasonably claim the minimum required to confirm they had something worth reporting to Kickstarter (note: a very different standard than "minimum required to confirm a bug") then no: call it "white hat" or "security research" or whatever else you want, but under the law it is very likely unauthorized access, and it's merely community norms protecting anyone at the WSJ who took part in exploring this bug. Do not fuck with other people's web applications unless you're sure it's OK. It's OK at Google and to an extent it is OK at Facebook, because both have published policies. I think that's what you should do for your applications, too; if you don't, the other community norm is "no policy means report the bug to Twitter instead of your security contact". You're obviously not going to go to jail (in the US) for not being careful about this stuff, but you can easily cost yourself 5 figures worth of legal fees and a whole lot of time and energy.