gnustep-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Subversion import #2


From: Andrew Ruder
Subject: Re: Subversion import #2
Date: Tue, 31 Jan 2006 17:10:49 -0600
User-agent: Mutt/1.5.9i

On Tue, Jan 31, 2006 at 11:44:55PM +0100, Quentin Mathé wrote:
> ok, I understand better now, it works well in my test.  Well, except I
> have to type my ssh password for every external  references, that's a
> real pain when you checkout the whole  'devmodules' content. It's even
> worse because I have this issue when  I update my working copy too
> (five passwords to type when I update  'core').  Any solutions ?

The simple answer, remove the password on your private key.

ssh -p -t rsa
ssh -p -t dsa

for example would allow you to change the password on your private key,
when it asks for a new password, just hit enter twice.  Security-wise,
this isn't -too- bad, but it does leave your private key unencrypted on
your disk.  If you fear the privacy of the files in your .ssh directory,
you may want to leave this as encrypted.

If you choose to leave them encrypted, you can use a program like
ssh-agent to cache your private key (and on disk you would still have
your encrypted private key).  I haven't used it before, but I think the
man page on ssh-agent is fairly descriptive.

The third answer, and this one is probably the best because it offers
huge speed benefits is to use the method described in my earlier email
about speeding up svn+ssh.  This one initiates a single ssh connection
to a host (you'll type your password that one time) and then every ssh
connection to that host feeds off of that master connection (until you
kill that instance of ssh of course).   

Hope that helps,
Andy

-- 
Andrew Ruder
http://www.aeruder.net




reply via email to

[Prev in Thread] Current Thread [Next in Thread]