Re:How a bug in VS2015 exposed my source code on GitHub and ...
by 15155 on Monday August 31, 2015 @07:57PM
(#10149852)
> mitigate the problem.
This seems like very minor engineering effort on behalf of GH - simple regexes, even.
Re:How a bug in VS2015 exposed my source code on GitHub and ...
by onion2k on Tuesday September 01, 2015 @01:45AM
(#10150919)
To detect the key, sure. But then there's the interface design to inform the user, hooking in to an email to notify the user if they're committing via git, a system to disable the option if necessary, monitoring the AWS format in case it changes, dealing with other formats that are requested by AWS's competitors, and so on.
I don't think this would be a minor undertaking or simple in any way, but it is important enough that a provider (and target) the size of GitHub should still do it.
Yes. The web service company should look at it as basic security - if people are using their service to discover private information and use it to defraud their users, even if the users have been stupid enough to upload that information publicly, the company should do what they can to mitigate the problem.
If I post a photo of my credit card on Twitter I would expect my bank to limit the damage as much as possible by declining obviously fraudulent transactions. Ultimately it's my own fault, and I would be liable for the costs, but that doesn't mean the bank should just let it happen if they can do something to stop it.