Re: Implementation Survey: How does your EAP peer/RADIUS proxy handle internationalization?

["Alan DeKok" <aland@ox.org>]

Bernard Aboba <aboba@internaut.com> wrote:
> 1. How is internationalization supported on your EAP peer implementation?

  The implementation enables internationalization, but doesn't fully
support it.[1]

> Does your EAP peer implementation support formating of the realm
> portion in IDN, or does it enable entering of UTF-8, or perhaps just plain
> ASCII?

  It enables entering UTF-8 text.

> 2. How is internationalization supported on your RADIUS proxy
> implementation?.

  The implementation enables internationalization, but doesn't fully
support it.[1]

> How does your implementation support internationalization within the realm
> table?  Are realm table entries stored in IDN, UTF-8, or something else?

  They are stored as NUL terminated C strings.[2]

> How are comparisons done between the realm in the NAI and the realm stored
> in the realm table?

  strcmp()

Notes: [1] If your file editor will write UTF-8 strings to the
configuration files, FreeRADIUS will read them and use them.  But it
will not print them as the appropriate UTF-8 glyphs in it's output or
log files.  Instead, it will print non-ASCII characters as
octal-encoded strings.  e.g "\303\301"

[2] The RADIUS client, server and EAP peer treat the strings as opaque
tokens for internal processing.  Therefore UTF-8 text may be entered,
or any other non-ASCII data, so long as it does not contain a NUL
(zero) character.

  Alan DeKok.

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