From: milki <milki@rescomp.berkeley.edu>
To: Sitaram Chamarty <sitaramc@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: optimising a push by fetching objects from nearby repos
Date: Sat, 10 May 2014 10:32:26 -0700 [thread overview]
Message-ID: <20140510173226.GA27483@hal.rescomp.berkeley.edu> (raw)
In-Reply-To: <20140510172338.GB45511@vauxhall.crustytoothpaste.net>
On 17:23 Sat 10 May , brian m. carlson wrote:
> I don't believe this is possible. There has been some discussion on
> related matters at least fairly recently, though.
>
> Part of the reason nobody has implemented this is because it exposes
> additional security concerns. If I create a commit that references an
> object I don't own, but is in someone else's repository, this feature
> could allow me to gain access to objects which I shouldn't have access
> to unless the authentication and permissions layer is very, very
> careful. This would make many very simple HTTPS and SSH setups much
> more complex. Alternates don't have this problem because they're done
> server-side.
If this were implemented service side and specified with, say, a config
option, would this security concern go away?
--
milki
next prev parent reply other threads:[~2014-05-10 17:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 13:39 optimising a push by fetching objects from nearby repos Sitaram Chamarty
2014-05-10 13:54 ` Duy Nguyen
2014-05-10 17:23 ` brian m. carlson
2014-05-10 17:32 ` milki [this message]
2014-05-10 20:04 ` brian m. carlson
2014-05-10 21:02 ` Junio C Hamano
2014-05-11 1:04 ` Sitaram Chamarty
2014-05-11 1:34 ` Storm-Olsen, Marius
2014-05-11 2:10 ` Sitaram Chamarty
2014-05-11 3:11 ` Storm-Olsen, Marius
2014-05-11 5:21 ` Sitaram Chamarty
2014-05-11 18:04 ` Junio C Hamano
2014-05-12 1:50 ` Sitaram Chamarty
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=20140510173226.GA27483@hal.rescomp.berkeley.edu \
--to=milki@rescomp.berkeley.edu \
--cc=git@vger.kernel.org \
--cc=sitaramc@gmail.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).