how to prevent bzr+ssh from asking a password each time I commit a change?

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mark Hammond wrote:

...

>>> Note that I'm not trying to argue that is a good model to use for
>>> authentication, but IMO it might explain where the perceptions and
>>> expectations comes from (and possibly will continue to come from)
>> What change are you proposing should happen?
> 
> I'm not proposing any change.  However, explaining away people's concerns with "being asked for a password or passphrase is SSH's business" is techically correct for bzr, but not for svn, and so doesn't really explain the situation to them nor cover their existing use-cases.  I was hoping to help people understand the underlying motivation for such questions so they are able to answer them in the most helpful way.
> 
> Cheers,
> 
> Mark

Interestingly, using TortoiseSVN with SSH does *not* cache any
credentials. You have to explicitly start pageant, and load in your ssh
key (manually). In fact, I'll often get prompted 2-3 times for doing
stuff like commit/log/etc.

So I don't think svn inherently caches all the time. Perhaps it always
caches for non ssh urls?

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjGk3IACgkQJdeBCYSNAANmhgCfQGS3c7kRGS20c/FCm6A1XbZ1
SNsAoNhsDMdB0F7rMTZP3DAolhQ99ggN
=Mw+H
-----END PGP SIGNATURE-----