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

[Pawel Widera]

On Thu, 24 Apr 2008, Pawel Widera wrote:

> 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.

I did some testing and find out that the client plain ASCII response is 
processed correctly. However, there is a small bug in handling username 
preventing client authorisation. I'm attaching the patch.

--
GnuPG: 0x230F845E
Jabber: address@hidden

digest-md5-server-patch.diff
Description: diff