3 ms·
Doesn't explain why it's dangerous. Unless you provide a PUT access to it. I explicitely leave .git on http, so that people may also clone it from there in ad
by informatimago 11y ago
Doesn't explain why it's dangerous.
Unless you provide a PUT access to it.
I explicitely leave .git on http, so that people may also clone it from there in addition to ssh and gitlab and github.
Seems to be of the same cagetory as http://www.dhmo.org/facts.html http://www.dhmo.org/facts.html
- detaro 11y agoThe article seems to be following the recent bunch of articles about web pages (that use git to deploy) leaving .git accessible and exposing source code or secrets. So not about access to public git repositories via HTTP, but accidentally exposing private repos by not protecting .git.