Thread (8 messages) 8 messages, 5 authors, 2016-08-11

Re: Locked down (but still shared) repositories

From: Rogan Dawes <hidden>
Date: 2016-08-11 20:11:33

Shawn Pearce wrote:
Johannes Schindelin [off-list ref] wrote:
quoted
On Thu, 7 Dec 2006, Shawn Pearce wrote:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help