git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arun Raghavan <ford_prefect@gentoo.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Nicolas Pitre <nico@fluxnic.net>, git@vger.kernel.org
Subject: Re: [PATCH 0/2] upload-pack: pre- and post- hooks
Date: Tue, 2 Feb 2010 11:22:18 +0530	[thread overview]
Message-ID: <6f8b45101002012152y76bccb65n78235fce170675ef@mail.gmail.com> (raw)
In-Reply-To: <20100201163618.GB9394@spearce.org>

On 1 February 2010 22:06, Shawn O. Pearce <spearce@spearce.org> wrote:
> Nicolas Pitre <nico@fluxnic.net> wrote:
>> On Mon, 1 Feb 2010, Shawn O. Pearce wrote:
>> I think such hooks could be allowed only if triggered explicitly by the
>> upload-pack caller, such as git-daemon.  That's probably the only
>> scenario where a useful use case can be justified for them anyway.
>>
>> And of course, to avoid any security problems, the actual hooks must not
>> be provided by the repository owner but provided externally, like from
>> git-daemon, via some upload-pack command line arguments.  This way the
>> hooks are really controlled by the system administrator managing
>> git-daemon and not by any random git repository owner.
>>
>> That should be good enough for all the use cases those hooks were
>> originally designed for.
>
> Oooh, I like that.
>
> If the paths to the hooks are passed in on the command line of
> git-upload-pack, and git-daemon takes those options and passes
> them through, you're right, we probably get everything we need.
>
> Gitosis can still use the hooks if it wants, since it controls
> the call of git-upload-pack.

I can add the uid check before running the hook as well. Is that good
enough, or would you guys like me to start from scratch with the
command-line argument approach?

Cheers,
-- 
Arun Raghavan
http://arunraghavan.net/
(Ford_Prefect | Gentoo) & (arunsr | GNOME)

  reply	other threads:[~2010-02-02  5:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-14 18:01 Removal of post-upload-hook Arun Raghavan
2010-01-14 19:36 ` Jeff King
2010-01-14 19:41   ` Shawn O. Pearce
2010-01-14 19:52     ` Arun Raghavan
2010-01-14 20:43     ` Jeff King
2010-01-14 21:06       ` Robin H. Johnson
2010-01-15 14:47         ` Jeff King
2010-01-15  6:12       ` Arun Raghavan
2010-01-15 11:52         ` Ilari Liusvaara
2010-01-15 12:14           ` Arun Raghavan
2010-02-01  8:32             ` [PATCH 0/2] upload-pack: pre- and post- hooks Arun Raghavan
2010-02-01  8:32               ` [PATCH 1/2] upload-pack: Reinstate the post-upload-pack hook Arun Raghavan
2010-02-01  8:32                 ` [PATCH 2/2] upload-pack: Add a pre-upload-pack hook Arun Raghavan
2010-02-01 15:20               ` [PATCH 0/2] upload-pack: pre- and post- hooks Shawn O. Pearce
2010-02-01 15:50                 ` Arun Raghavan
2010-02-01 16:01                   ` Shawn O. Pearce
2010-02-02  5:50                     ` Arun Raghavan
2010-02-01 16:30                 ` Nicolas Pitre
2010-02-01 16:36                   ` Shawn O. Pearce
2010-02-02  5:52                     ` Arun Raghavan [this message]
2010-02-02  6:15                       ` Nicolas Pitre

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=6f8b45101002012152y76bccb65n78235fce170675ef@mail.gmail.com \
    --to=ford_prefect@gentoo.org \
    --cc=git@vger.kernel.org \
    --cc=nico@fluxnic.net \
    --cc=spearce@spearce.org \
    /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).