Joe Orton wrote:
On Thu, Jan 12, 2006 at 06:37:41PM +0100, steveking wrote:
We've already got a couple of reports from users using the 1.3.0RC1/2
versions of TortoiseSVN that they can't connect to their repositories
anymore because of this. Some could make it work by disabling the guest
account, but some of them simply can't disable that account because they
need it.
Do you have an idea on how to solve this? Maybe a new option for
mod_auth_sspi to not authenticate as user "guest"? Or is a change in
neon required? Or in Subversion?
Maybe the whole SSPI auth feature could be made run-time configurable in
neon and not compile-time configurable?
Yes, allowing the application to select which auth protocols to enable
is something that's on the TODO list. (it is relatively simple to
implement in neon, but requires some new interfaces; making it
configurable in Subversion is probably more work)
I'd really appreciate it if you could implement those interfaces in neon
soon. Once that's done, I can try (or maybe someone else more familiar
with Subversion) to implement this in the Subversion lib.
Right now, I've disabled SSPI support in the 1.3.x versions of TSVN:
it's better to not introduce new features which can prevent existing
users to connect to their repository without any chance of working
around it with an option/setting/whatever.
It's enabled on TSVN trunk however, so I can run tests and let others
test it as well.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
_______________________________________________
neon mailing list
[email protected]
http://mailman.webdav.org/mailman/listinfo/neon
