From: Shawn Pearce <spearce@spearce.org>
To: Rogan Dawes <discard@dawes.za.net>
Cc: git@vger.kernel.org
Subject: Re: Locked down (but still shared) repositories
Date: Thu, 7 Dec 2006 15:16:25 -0500 [thread overview]
Message-ID: <20061207201625.GA12502@spearce.org> (raw)
In-Reply-To: <45786F5A.6020400@dawes.za.net>
Rogan Dawes <discard@dawes.za.net> wrote:
> Shawn Pearce wrote:
> >In the situation you describe everyone looks the same to the
> >update hook...
>
> See Section 8.2.6.1
>
> http://www.unix.org.ua/orelly/networking_2ndEd/ssh/ch08_02.htm
>
> You should be able to do something similar for git as they do for SSH.
Ok, I just learned something new. Thank you!
Forced commands on a per-key basis would certainly work. I'm not
settled on the idea as the end solution, but it does seem to be
perhaps slightly better than the setuid approach.
--
next prev parent reply other threads:[~2006-12-07 20:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 11:35 Locked down (but still shared) repositories Shawn Pearce
2006-12-07 12:21 ` Martin Waitz
2006-12-07 15:42 ` Johannes Schindelin
2006-12-07 19:17 ` Shawn Pearce
2006-12-07 19:45 ` Rogan Dawes
2006-12-07 20:16 ` Shawn Pearce [this message]
2006-12-07 20:16 ` Randal L. Schwartz
2006-12-07 20:32 ` Rogan Dawes
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=20061207201625.GA12502@spearce.org \
--to=spearce@spearce.org \
--cc=discard@dawes.za.net \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.