Re: git + ssh + key authentication feature-request
- From
Alan Chandler <alan@chandlerfamily.org.uk>
- Date
- Feb 8, 2006, 23:35 UTC
- Message-ID
- <200602082335.42449.alan@chandlerfamily.org.uk>
- In-Reply-To
- <43EA7D57.7040409@iaglans.de>
On Wednesday 08 February 2006 23:23, Nicolas Vilz 'niv' wrote:
Show 5 quoted lines
> 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.