Git development
 help / color / mirror / Atom feed
From: Alan Chandler <alan@chandlerfamily.org.uk>
To: git@vger.kernel.org
Subject: Re: git + ssh + key authentication feature-request
Date: Wed, 8 Feb 2006 23:35:42 +0000	[thread overview]
Message-ID: <200602082335.42449.alan@chandlerfamily.org.uk> (raw)
In-Reply-To: <43EA7D57.7040409@iaglans.de>

On Wednesday 08 February 2006 23:23, Nicolas Vilz 'niv' wrote:

> 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..

This sounds like you haven't got sshd set up correctly.  You can get it to log 
you in soley based on keys, and whether or not you give a password is then 
dependent soley on whether your private key has a pass phrase or not and then 
whether or not you are using some ssh-agent to remember them for you.

I have it setup so that access to ssh controlled accounts is soley via key.

Private keys remaining on fixed computers at home have no passphrase, my 
laptop has a private key with a passphrase which I enter once on login.

I have several accounts around the place with my public keys enumerated in 
their .ssh/authorized_keys file, so I have been able to contact git 
repositories with urls like

git@www.chandlerfamily.org.uk
www-data@www.chandlerfamily.org.uk
 and for my own account
just www.chandlerfamily.org.uk

all without entering a password.

But following the discussion thread Junio pointed to I have converted 
everything to shared repositories and I now only use my own account to log 
in.

-- 
Alan Chandler
http://www.chandlerfamily.org.uk
Open Source. It's the difference between trust and antitrust.

      parent reply	other threads:[~2006-02-08 23:35 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'
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 [this message]

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=200602082335.42449.alan@chandlerfamily.org.uk \
    --to=alan@chandlerfamily.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox