[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: Philip Martin <philip.martin_at_wandisco.com>
Date: Wed, 07 Dec 2011 10:39:03 +0000

Philip Martin <philip.martin_at_wandisco.com> writes:

> Victor Sudakov <sudakov_at_sibptus.tomsk.ru> writes:
>
>> Philip Martin wrote:
>>>
>>> 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:
>
> I'm not a SASL expert, what does anonymous do? Does that give the
> client a choice? Can you use "mech_list: gssapi"?

One other thing is there is a note in
http://svn.apache.org/repos/asf/subversion/trunk/notes/sasl.txt that
states that setting the client's max-encryption to more than 56 will
prevent GSSAPI working. I don't know whether that is still true or
out-of-date, or why this should suddenly be an issue when going from 1.6
to 1.7.

-- 
uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com
Received on 2011-12-07 11:39:40 CET

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