Re: Bug: RFC2831 noncompliance - "charset=utf-8" in challenge REQUIRES "charset=utf-8" in response

[Pawel Widera]

The daily snapshot from 2008-04-12 (Saturday) has been installed on
chrome.pl. Unfortunatelly authentication problem is still there (can't
connect using pidgin, gajim or gossip):
http://jabberd2.xiaoka.com/ticket/200

It might be worth noticing that chrome.pl server used once this patch to 
fix the validation:
http://jabberd2.xiaoka.com/browser/trunk/contrib/gsasl-charset-validate-fix.
diff

I think that to properly test the solution for this you need to use both 
username and password being plain ASCII. If one of these is UTF-8 it 
simply triggers the UTF-8 response and authentication works fine. The 
problem here is about acepting ASCII response even if server advertised 
itself as UTF-8 capable.

--
MoMaT