kerberos authentication using ankhsvn and tortoisesvn

-----Original Message-----
From: Blaž Lorger
Sent: 11. junij 2010 7:48
To: 'users_at_subversion.tigris.org'; 'users_at_tortoisesvn.tigris.org'; 'users_at_ankhsvn.open.collab.net'
Subject: kerberos authentication using ankhsvn and tortoisesvn

Hi,

Recently I also experienced problems with SVN clients using Kerberos authentication. There are no problems with clients using svn lib 1.6.6 (Slik-Subversion-1.6.6-win32.msi, TortoiseSVN-1.6.6.17493-win32-svn-1.6.6.msi and AnkhSvn-2.1.7444.278.msi). I first started having problems with clients using svn lib 1.6.9 and this also remains true for svn lib 1.6.11 (Slik-Subversion-1.6.11-win32.msi, TortoiseSVN-1.6.8.19260-win32-svn-1.6.11.msi and AnkhSvn-2.1.8420.8.msi).

At first problem was not so bad, since authentication worked most of the time. Problems occurred only when large amount of data was exchanged between client and server. But recently Kerberos authentication failed completely. This seems to coincide with upgrade of mod_auth_kerb on corporate SVN servers. My guess is that server side change contributes to reliable problem manifestation, but basic problem is in svn library, since older SVN versions work fine.
There are also no problems when web server is accessed through regular browser (Firefox, IE).

It seems that SVN client actually sends Kerberos ticket to server once, but then "forgets" to attach same ticket on subsequent HTTP requests.

I've produced Neon trace (attachment) with Slik-Subversion, hopefully this will help to diagnose the problem. Trace was produced when following command was executed on up to date working copy:
        svn update --config-option servers:global:neon-debug-mask=1023 --config-option servers:global:http-auth-types=negotiate >trace 2>&1

First noticeable thing in trace is change in lib neon version from 0.29.0 to 0.29.3. My guess is that problem is in this library.

Blaž