Subversion 1.3 has support for neon 0.25.x, which is really good because
of the possibility to interrupt connections (e.g. when doing 'svn log
--limit'). But neon 0.25.x also has support for SSPI authentication with
a windows domain.
Now, TortoiseSVN-1.3.0RC1 is linked with Subversion 1.3 and neon 0.25.4.
Fortunately, some people are already using and testing that RC release.
Which brings me to the report:
If a user isn't part of a domain, but tries to connect to a repository
located on a windows domain (with the mod_auth_sspi module installed),
TortoiseSVN doesn't work. It seems to go on forever trying to
authenticate, without ever falling back to asking username/password as
we would expect.
Everything works ok if the user is part of the same domain as the
repository, then the SSPI auth works without any problems and without
the need to ask for username/password.
I've searched the neon mailing list. It seems the problem is not unknown:
Joe Ortons answer there was that the problem isn't in neon but in the
lib using it, referring to the creds callback.
I don't know enough about neon/svn_ra_dav to even guess if the bug is in
neon or Subversion, so I'd like to ask you guys to investigate this
problem. Another problem I have is that I don't have access to a repo
hosted on a windows domain for at least two weeks (we're renovating our
office, so our PC's there are stacked up in a storage room).
And even if I had my PC there, network is disabled for PC's not part of
the domain, so I couldn't test this setup.
Maybe related, maybe not:
Our office is behind a proxy which rejects REPORT requests. With a 1.2.x
Subversion client I get a "REPORT request failed" error when I try to
access e.g. the neon repository. But with an 1.3.0 client, I get a
"working copy locked" error after about five minutes.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Jan 6 20:10:53 2006