Re: svn+ssh asks password twice

On Mon, Nov 16, 2009 at 5:51 PM, Stefan Sperling <stsp_at_elego.de> wrote:
>
> Can you provide a working example invocation of svn using svn+ssh
> where two authentication steps are required for the same run of
> the svn program, without externals involved?

svn co svn+ssh://svn.server.com/bla/bla/bla
   bla/bla/bla should exist or else only one step is needed.

svn diff -r x:y
svn st -u
   two requests

There can be more, but everything else I've tried uses one request so far:
svn up
svn switch
svn ls
svn blame
svn ci

>> I want to enter a bug report, but because of "buddy
>> system" I mail it here first.
>
> Good :)

I still hesitate. It is still only three operations that require two
connections, but there can be more - merge, for example.

It can be eventually two tickets - the second one for reusing
connection for svn:externals from the same repository.

> Subversion should make re-using credentials possible when connecting
> to the same repository twice (e.g. an external pointing somewhere into
> the same repository). I haven't checked but don't think Subversion does
> that right now.

I've checked. It doesn't. =)

> With other repository access methods, it's also possible to have
> your Subversion password cached on disk encrypted, so you don't
> have to enter it.

It is a strict requirement that password should be entered manually.
Subversion is used for deployment. Tag is created to fetch code from
various paths of repository trunk and branches via svn:externals.
Every operation should be confirmed by password to avoid any
casualties ("oops, wrong window" stuff).

Thanks to this discussion I now think about making a SSH key with
password, but key management for every developer with SSH account who
can make a deployment could be a problem.

https:// method won't work, because there is already an Apache2 there
with a lot of custom dependencies. Running two Apache2 instances on
443 port is impossible and running two Apache2s on separate ports is
not a solution, because there is also Apache 1.3 for some legacy
applications (even though it's Debian Lenny). I do not want to make
things more complicated than they already are. =) I also do not want
to maintain another file with SVN accounts when everybody has SSH.

Please, CC.

-- 
anatoly t.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2419047
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].