* RFC: "refs only" restriction for snapshots
@ 2017-04-24 19:52 mricon
0 siblings, 0 replies; only message in thread
From: mricon @ 2017-04-24 19:52 UTC (permalink / raw)
Hello:
It would be nice to be able to restrict snapshots only to refs, both for
sanity and for potential security reasons. E.g. see the "Security"
section here:
https://git-scm.com/docs/git-upload-archive
My concern is mostly rogue crawlers that ignore robots.txt and try to
request tarballs for each commit they find (doing HEAD, which appears to
be enough to trigger full-blown response with tarball generation). At
least if snapshot links were only generated for refs, that would reduce
the impact.
In the meantime, this is easy enough to restrict via the http server,
but this is not the best UX if links are listed, but clicking on them
results in an error message.
Perhaps some setting like "snapshots-refsonly: 0/1"
Best,
-K
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2017-04-24 19:52 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-04-24 19:52 RFC: "refs only" restriction for snapshots mricon
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).