All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Vilz 'niv' <niv@iaglans.de>
To: git@vger.kernel.org
Subject: Re: git + ssh + key authentication feature-request
Date: Thu, 09 Feb 2006 01:33:30 +0100	[thread overview]
Message-ID: <43EA8DDA.3070906@iaglans.de> (raw)
In-Reply-To: <7v4q39o3xs.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:
> Nicolas Vilz 'niv' <niv@iaglans.de> writes:
> 
> 
>>in my case it would be only one system-user which has full access to
>>several repositories. At this time, the users which use that account,
>>have to give a password, which isn't that bad... it would be easier
>>and more secure for me, not to give a password, but ask the users for
>>the ssh pubkey..

[... how sshd operates ...]

> You _could_ tell them to use the same -l option and log-in as
> the same UNIX user with their own keys, though.  But that way
> you cannot tell which developer pushed into the repository (of
> course if you trust the commits, commit log message would say
> the committer ident).

I think this (last) scenario would match my thoughts best :)

Exactly that was, what i was trying to do, although I couldn't tell git 
to send my identify-file. That was (more or less) my initial-question 
(howto do that, the ssh option -i) :)

You got a point which i haven't recognized, yet...

I really can't tell later on which developer pushed unless i trust the 
commit-messages. I will think about that.

So, how do i tell git to send my identity-file to sshd? And could I set 
an alias like in .git/remotes for that location / identity?

Thank you very much for your explanations and help.

Sincerly
Nicolas

  parent reply	other threads:[~2006-02-08 23:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-08 22:42 git + ssh + key authentication feature-request Nicolas Vilz 'niv'
2006-02-08 21:58 ` Junio C Hamano
2006-02-08 23:23   ` Nicolas Vilz 'niv'
2006-02-08 22:45     ` Linus Torvalds
2006-02-09  0:43       ` Nicolas Vilz 'niv'
2006-02-08 22:56     ` Junio C Hamano
2006-02-09  0:14       ` Mark Wooding
2006-02-09  0:40         ` Junio C Hamano
2006-02-09  0:55           ` Mark Wooding
2006-02-09  0:33       ` Nicolas Vilz 'niv' [this message]
2006-02-08 23:50         ` Linus Torvalds
2006-02-09  1:16           ` Nicolas Vilz 'niv'
2006-02-08 23:55         ` Junio C Hamano
2006-02-09  1:06           ` Nicolas Vilz 'niv'
2006-02-08 23:35     ` Alan Chandler

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=43EA8DDA.3070906@iaglans.de \
    --to=niv@iaglans.de \
    --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.