summaryrefslogtreecommitdiff
path: root/commit-graph.c
diff options
context:
space:
mode:
authorJeff King <peff@peff.net>2024-04-16 04:52:13 -0400
committerJohannes Schindelin <johannes.schindelin@gmx.de>2024-04-17 22:29:57 +0200
commite69ac42fcc866d3d6f84ea42bc656673440a07f5 (patch)
treea8ec59fc23e05b5d9cc26e2454d3e41998c7b268 /commit-graph.c
parent7b70e9efb18c2cc3f219af399bd384c5801ba1d7 (diff)
docs: document security issues around untrusted .git dirs
For a long time our general philosophy has been that it's unsafe to run arbitrary Git commands if you don't trust the hooks or config in .git, but that running upload-pack should be OK. E.g., see 1456b043fc (Remove post-upload-hook, 2009-12-10), or the design of uploadpack.packObjectsHook. But we never really documented this (and even the discussions that led to 1456b043fc were not on the public list!). Let's try to make our approach more clear, but also be realistic that even upload-pack carries some risk. Helped-by: Filip Hejsek <filip.hejsek@gmail.com> Helped-by: Junio C Hamano <gitster@pobox.com> Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Diffstat (limited to 'commit-graph.c')
0 files changed, 0 insertions, 0 deletions