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

Re: GSSAPI auth stopped working after upgrade

From: Victor Sudakov <sudakov_at_sibptus.tomsk.ru>
Date: Wed, 7 Dec 2011 17:22:24 +0700

Philip Martin wrote:
> > I have upgraded the svn client from subversion-1.6.17 to
> > subversion-1.7.2 on FreeBSD 7.4 and GSSAPI authentication stopped
> > working. svn does not even try to get a Kerberos ticket and tries to
> > use DIGEST-MD5 at once. The server is still subversion-1.6.16_1 (no
> > changes there).
> >
> > What has happened and how can I get back my GSSAPI? Please help. Need
> > I now to enable something on the client side?
> >
> > If I disable the digest-md5 mech on the server, like
> > (mech_list: gssapi anonymous), I get:
> Few Subversion developers have worked on the SASL code, there may be
> more SASL expertise on the users list.
> I seem to recall an issue about choosing the mechanism: the server
> expects the client to choose the most suitable, but the client expects
> the server to suggest the most suitable and so doesn't have any sort of
> selection hierarchy. Perhaps that is the problem?
> Have you tried with "mech_list: gssapi" so that the client has no choice?

Yes, in fact I wrote about it in the original post. I repeat:

If I disable the digest-md5 mech on the server, like
(mech_list: gssapi anonymous), I get:

$ svn co svn://big/configs
svn: E210007: Unable to connect to a repository at URL 'svn://big/configs'
svn: E210007: Cannot negotiate authentication mechanism

I even googled for the "Cannot negotiate authentication mechanism"
message but have only come up with some Windows specific problems like
TortoiseSVN being unable to find a dll.

Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
Received on 2011-12-07 11:23:00 CET

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