On 07.11.20 00:22, Ian Eldred Pudney wrote:
This input causes libidn2 to report a disallowed character. This appears to not be a "bug", but rather out-of-date tables in libidn2. The offending character <https://www.fileformat.info/info/unicode/char/0e90/index.htm> was only added to Unicode in 2019.

  * Domain name:

    ຐ.xyz <http://xn--46c.xyz>

  * Domain name hex codepoints:

    ['e90', '2e', '78', '79', '7a']

  * Punycode:

    xn--46c.xyz <http://xn--46c.xyz>


Libidn2 is based upon the IANA/IETF review which currently is based on Unicode 11.0. That means we consider IANA (and not the Unicode Consortium) to be authoritative regarding internet standards.

https://www.iana.org/assignments/idna-tables-11.0.0/idna-tables-11.0.0.xhtml#idna-tables-context

https://tools.ietf.org/html/rfc8753

Regards, Tim

Attachment: OpenPGP_0x08302DB6A2670428.asc
Description: application/pgp-keys

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to