Re:GitHub and Rails: You have let us all down.
by nirvdrum on Sunday March 04, 2012 @06:48PM
(#3664624)
It's sort of a sticky situation. My take on it wasn't that this was so much to screw with GitHub as it was to show the Rails team the true severity of an issue they downplayed. It gets a bit circuitous because Rails is hosted on GitHub and GitHub is a Rails app. Had he reported it to GitHub and they patched it, which is arguably the proper thing to have done, nothing would have happened on the Rails side of the equation. All told, I think he did the right thing.
Re:GitHub and Rails: You have let us all down.
by mason55 on Sunday March 04, 2012 @06:46PM
(#3664620)
The reason for exploiting github was to get the rails issue noticed, not to notify github of a vuln. If he quietly notifies github then there are still thousands of github sites out there that remain vulnerable. By exploiting GitHub and getting this huge response he allows the news of the vulnerability to get tons more coverage than it would have otherwise.
Re:GitHub and Rails: You have let us all down.
by hythloday on Sunday March 04, 2012 @07:15PM
(#3664705)
He notified Github "last Friday", according to them:
https://github.com/blog/1068-public-key-security-vulnerabili...
Re:GitHub and Rails: You have let us all down.
by stock_toaster on Sunday March 04, 2012 @07:24PM
(#3664729)
> His previous report was fixed last friday
Makes it sound like a separate issue.
edit: looks like github clarified https://github.com/blog/1069-responsible-disclosure-policy
Re:GitHub and Rails: You have let us all down.
by hythloday on Sunday March 04, 2012 @07:39PM
(#3664782)
Same exploit, different endpoint. Github agree they "should have...immediately looked for related issues":
https://twitter.com/#!/technoweenie/status/17645071550868684...
...though as they've now unbanned his account (good on them), it's somewhat moot.
Re:GitHub and Rails: You have let us all down.
by stock_toaster on Sunday March 04, 2012 @08:04PM
(#3664865)
Aha. Thanks for the extra info.
If he didn't actually contact github directly and just assumed they would see the rails issue on a weekend, then I wouldn't exactly call it 'notice'.
If he did submit it to github via the proper channels before taking action, and nothing was done within a reasonable timeframe (eg. not just an hour or two on a sunday), then what he did would make a bit more sense.