News for hackers. Stuff that matters.
Re:Don't publicly expose .git (2015) by libeclipse on Sunday June 11, 2017 @08:40PM (#14534593)
The author fails to acknowledge a scenario where you wouldn't care, or where you'd even actively want your source code to be public.

For example, static websites for open source projects, et al.

Re:Don't publicly expose .git (2015) by codezero on Sunday June 11, 2017 @08:53PM (#14534628)
I think they did...

> It seemed like an accessible git repository was intended on some websites - mostly open source projects where the website’s sourcecode is available online.

Re:Don't publicly expose .git (2015) by ubernostrum on Monday June 12, 2017 @12:25AM (#14535191)
Every so often, the Django security address gets an email from someone who wants to claim bug-bounty money because "Dear Django team, I have discovered source-code disclosure vulnerability in your web site..."
Re:Don't publicly expose .git (2015) by xg15 on Monday June 12, 2017 @04:55AM (#14535901)
Even then though, they should be aware of the meta data that's stored in the repo and make sure it's appropriately sanitized.

> On the other side, we had to hold our breath when we noticed that more than 100 projects used HTTP-Authentication for server-client communication. That means, that the protocol://user:password@host/repository combination is saved in the .git/config file, giving attackers access to the users (companies) GitLab-instance or GitHub/BitBucket account. With a bit of luck an attacker gets access to the CI-Server and then runs malicious code to further compromise your infrastructure.