ftblog

So, my first lazyweb posting. Let's see how this works out. Can't quite work
any worse than trying to ask #svn or the subversion users mailing list, where
the unanimous reaction to my question was utter silence...

There is actually at least one guy who asked about the same thing as I did,
receiving the same kind of cold silence. :)

The problem is quickly described:

When trying to work on a subversion repository with a 1.6.5 subversion command
line client on windows, it barfs:

Cannot negotiate authentication method

The server is a 1.6.4 svnserve on debian stable (from backports), using sasl
authentication and encryption. The server works. How can I be sure? Well,
about *every* *other* client works. TortoiseSVN? Works. TkCVS? Works. ESVN?
Works. Linux svn command line client? Works. So, yeah, I'm pretty damn sure
the server is working correctly.

The svn command line client for windows was downloaded from tigris.org and
its 'svn --version' output would suggest, that SASL support is in fact
included.

I wouldn't bother with the command line client on windows, but unfortunately,
in the lab right here, we're using a PCB software that interfaces to
subversion checkouts via the windows svn command line client. Of course, the
PCB software isn't available on non-windows systems; so basically, we're
fucked right here... (yeah yeah, I *can* work around the problem using
TortoiseSVN, but that makes the PCB software behave rather weird, when I
update the repository with changes from a co-worker.)

If anyone has got a clue as to what the problem might be, please send me a
mail. I'd really appreciate it...