Subversion 1.3.0 and neon 0.25.x

[Stefan Küng <to...@gmail.com>]

Hi,

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:
http://mapcar.org/tsvn-snapshots/1.3.x/TortoiseSVN-1.3.0.5362-dev-svn-1.3.0.msi
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.

Stefan

-- 
        ___
   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