Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare

[Stefan Winter <stefan.winter@restena.lu>]

Hi,

> Unfortunately, in at least some implementations, this is not the case. 
> However, I'd be interested if there exist implementations that handle
> UTF-8 usernames.  That would provide a reference to test a fix against.  
>   

Indeed. After some more tests:

Lancom Client Utility (same Windows XP instance):
-------------------------------------------------------------------------
behaviour is the same as the built-in supplicant: encoded on the wire in
locale, cyrillic input possible but transscribed to "?".

KNetworkManager (openSUSE Linux 11.0, 32-Bit)
-----------------------------------------------------------------------

encoding of @müller.de to @m[0xC3][0xBC]ller.de (UTF-8, no punycode)
encoding of cryillic characters to 2-byte encodings starting with d0 and
d1 -> looks like cyrillic area of UTF-8, no punycode in realm

That looks like a good UTF-8 test case. KNetworkManager uses
wpa_supplicant as a backend.

Greetings,

Stefan Winter

P.S.: add $OPEN_SOURCE_SALES_PITCH_FOR_WPA_SUPPLICANT here ;-)

-- 
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>