How a bug in VS2015 exposed my source code on GitHub and cost me $6,500

Re:How a bug in VS2015 exposed my source code on GitHub and ... by LeonB on Monday August 31, 2015 @09:03PM (#10150096)

> all this, apparently, is laid at the feet of Visual Studio

I wonder if you actually read the story.

He admits several faults including most if not all of those you mention.

[ Parent | on HN ]

Re:How a bug in VS2015 exposed my source code on GitHub and ... by inopinatus on Monday August 31, 2015 @09:14PM (#10150141)

So what? Admitting fault isn't absolution. He really does go out of his way to blame the tools.

[ Parent | on HN ]

Re:How a bug in VS2015 exposed my source code on GitHub and ... by schrodinger on Tuesday September 01, 2015 @12:14AM (#10150691)

The tool has a huge bug! Even if he wasn't putting credentials in there, it could still have led to sensitive source code getting out or something!

[ Parent | on HN ]

Re:How a bug in VS2015 exposed my source code on GitHub and ... by x0n on Tuesday September 01, 2015 @09:40AM (#10152210)

Article updated - VS wasn't the issue. He had installed a 3rd party github extension (from github themselves) that overrides the built-in Git support in visual studio... bug was found, confirmed and fixed yesterday though, so a quick turnaround.

[ Parent | on HN ]