4 ms·
He didn't hack into any others' accounts, he simply (mis)used the service from his own. Suspending him is useless for security as he could set up another accoun
by ricardobeat 15y ago
He didn't hack into any others' accounts, he simply (mis)used the service from his own. Suspending him is useless for security as he could set up another account in minutes.
- eli 15y agoReally splitting hairs here. He committed a change to a repository that wasn't his. He altered files that belong to other users, albeit benignly.
- andrewcooke 15y agothe post at https://github.com/blog/1068-public-key-security-vulnerability-and-mitigation https://github.com/blog/1068-public-key-security-vulnerabili... says "Database and log analysis have shown that the user compromised three accounts (rails and two others that appear to have been proofs of concept)." do you have any evidence for your assertion? (and why the downvote? i'm just reporting the facts....)
- skeletonjelly 15y agoI think the accounts mean organisations. For instance, he exploited this vulnerability to add his public key to the authorised rails user keys. He probably did this to two other "accounts". His exploit wasn't logging in or impersonating any other accounts AFAIK.