Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare
Bernard Aboba wrote:
> " The CUI is often created as "hash at example.com". i.e. based off of the
> User-Name. So it's worth double-checking the effects of changing
> User-Name on all down-stream uses."
>
> Presumably the hash can be calculated on UTF-8 as well as ASCII, no?
Yes. If the "example.com" portion is interpreted by any party, it has
to be dealt with the same as the corresponding portion of the User-Name.
Alan DeKok.
_______________________________________________
Emu mailing list
Emu at ietf.org
https://www.ietf.org/mailman/listinfo/emu
- References:
- [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare
- Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare
- Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare
- Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare
- Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare
- Prev by Date:
Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare
- Next by Date:
Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare
- Previous by thread:
Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare
- Next by thread:
Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare
- Index(es):
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.