Re:One in every 600 websites has .git exposed
by bsg75 on Sunday July 26, 2015 @08:27PM
(#9952758)
Would it be safer to not put .git within the reach of the webserver, and separate the development path from the production host path?
[ Parent
| on HN ]
Re:One in every 600 websites has .git exposed
by bbcbasic on Sunday July 26, 2015 @08:41PM
(#9952794)
It certainly would, however like another comment I replied to ITT security doesn't have to be either-or it can be "do all the secure things".
I.e.
* No secrets in your repo
* Only copy to the server what you need (and automate this)
* Add conditions to your web server to not serve up .git, in-case the previous two checks failed.
When working in teams I think having additional checks and balances and not one 'perfect solution' is vital.
Re:One in every 600 websites has .git exposed
by danieltillett on Sunday July 26, 2015 @09:18PM
(#9952890)
Extremely good point - we should always aim for security in depth and especially don’t rely on people not doing stupid things, because if it is possible then someone will at some point.