[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Subversion 1.3.0 and neon 0.25.x

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2006-01-07 20:03:33 CET


Neon versions 0.25.0 up to 0.25.4 have sspi authentication implemented.
But it doesn't work correctly.
If a user isn't part of a domain at all or not part of the same domain
the repository is set up to authenticate against, neon goes into an
endless loop authenticating over and over again. This is very bad,
because it won't fall back to basic authentication, which means users
trying to access their company repository from home can't use such a
Subversion client at all.

This of course also affects Subversion. So I suggest to tweak the build
scripts to undefine HAVE_SSPI until neon is fixed. Or use neon < 0.25.0
(which would mean to loose the features of interrupted connections) for
the windows builds.

I've worked out a patch for neon, but I want to wait for TSVN users to
test it first before I send it in (my last try of a patch wasn't that
successful). If you want to help testing it:
has the patch already applied.
It should be able to automatically authenticate if you're part of the
same domain as the repository, but fall back to basic auth (ask for
username/password) if you're not.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 7 20:04:13 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.