Incident Report: Inadvertent Private Repository Disclosure

Re:Incident Report: Inadvertent Private Repository Disclosure by Normal_gaussian on Friday October 28, 2016 @03:11PM (#12819625)

Datacentre's have outstanding track records, and if you secure your box correctly there are few ways to compromise it. On-premise will either be incredibly costly or missing key protections or infrastructure.

Self-hosted git (through the many installable git servers or raw git) running on a correctly sized box is almost certainly the way to go

[ Parent | on HN ]

Re:Incident Report: Inadvertent Private Repository Disclosure by newsat13 on Friday October 28, 2016 @06:21PM (#12821268)

This github vulnerability has nothing to do with insecure box. It has to do with a bad application logic. This can happen anywhere - self-hosted or not.

[ Parent | on HN ]

Re:Incident Report: Inadvertent Private Repository Disclosure by bsder on Friday October 28, 2016 @06:42PM (#12821386)

That is true. But, if I'm running my own instance, the probability is that it doesn't matter if someone else gets access via bad application logic. Everybody is probably employed by the same company.

It's a difference of degree: compromising my self-hosted or on-premise server means that somebody already in my employ has more access than they should. If I'm a small organization, that probably doesn't matter. If I'm a big organization, I probably have an IT staff to deal with this and the people involved are still "nominally" under my control.

The github mistake means that people completely unrelated to my repository can get access.

[ Parent | on HN ]

Re:Incident Report: Inadvertent Private Repository Disclosure by ifhs on Friday October 28, 2016 @09:20PM (#12822092)

Well, the code can simply be made public by bad application logic. Which is why I thought you where talking of on premise where the intranet will seal off outsiders

[ Parent | on HN ]