From: Rogan Dawes <discard@dawes.za.net>
To: Shawn Pearce <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: Locked down (but still shared) repositories
Date: Thu, 07 Dec 2006 21:45:30 +0200 [thread overview]
Message-ID: <45786F5A.6020400@dawes.za.net> (raw)
In-Reply-To: <20061207191730.GA12143@spearce.org>
Shawn Pearce wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
>> On Thu, 7 Dec 2006, Shawn Pearce wrote:
>>
>>> For various auditing reasons the repositories need to be tightly
>>> controlled. That is the following cannot be permitted:
>>>
>>> [...]
>> How about just one such user? After all, you already have this user: the
>> repo owner. Of course, people have to push via ssh, even on the same
>> machine.
>
> How do I know which SSH key the client used to connect? Remember I'm
> looking at the real uid to determine who is performing the operation.
> In the situation you describe everyone looks the same to the
> update hook...
>
> For (probably stupid) reasons the server is the commerial F-Secure
> SSH server, btw. So OpenSSH based things wouldn't apply. And best
> that I can tell, F-Secure SSH won't tell me which key was used
> to authenticate.
>
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.
Rogan
next prev parent reply other threads:[~2006-12-07 19:45 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 [this message]
2006-12-07 20:16 ` Shawn Pearce
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=45786F5A.6020400@dawes.za.net \
--to=discard@dawes.za.net \
--cc=git@vger.kernel.org \
--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 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.