Re: Subversion migration finished
- From: "Kalle Vahlman" <kalle vahlman gmail com>
- To: Bill Haneman sun com
- Cc: gnome-i18n gnome org, gnome-infrastructure gnome org, gnome-hackers gnome org, devel-announce-list gnome org, Ross Golder <ross golder org>, Martyn Russell <martyn imendio com>, gnome-doc-list gnome org
- Subject: Re: Subversion migration finished
- Date: Tue, 2 Jan 2007 19:56:45 +0200
2007/1/2, Bill Haneman <Bill Haneman sun com>:
By the way, when using svn over ssh I now have to authenticate three
times when doing a cvs co. Is this a known 'feature' ?
Yes:
http://svnbook.red-bean.com/en/1.1/ch06s03.html
"When using svn+ssh:// URLs to access a repository, remember that it's
the ssh program prompting for authentication, and not the svn client
program. That means there's no automatic password caching going on
(see the section called "Client Credentials Caching"). The Subversion
client often makes multiple connections to the repository, though
users don't normally notice this due to the password caching feature.
When using svn+ssh:// URLs, however, users may be annoyed by ssh
repeatedly asking for a password for every outbound connection. The
solution is to use a separate SSH password-caching tool like ssh-agent
on a Unix-like system, or pageant on Windows."
And about the Client Credentials Caching:
http://svnbook.red-bean.com/en/1.1/ch06s02.html#svn-ch-6-sect-2.2
IMO it's better to have your public key in ~/.ssh/authorized_keys on
the server though, but it depends on the server policy if this is
allowed (or even helps, sshd might be configured to not allow
non-interactive logins).
--
Kalle Vahlman, zuh iki fi
Powered by http://movial.fi
Interesting stuff at http://syslog.movial.fi
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]