From: mricon at kernel.org (Konstantin Ryabitsev)
Subject: RFC: "refs only" restriction for snapshots
Date: Mon, 24 Apr 2017 15:52:26 -0400 [thread overview]
Message-ID: <20170424195226.GF15623@gmail.com> (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
reply other threads:[~2017-04-24 19:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170424195226.GF15623@gmail.com \
--to=cgit@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).