diff options
author | 2017-05-09 21:56:34 -0400 | |
---|---|---|
committer | 2017-05-11 14:25:01 -0400 | |
commit | 87057e244b4d2e723dc98b2b3cef1901c155f005 (patch) | |
tree | c7505157bfa7609a15700082336e4f04311243cd /README | |
parent | 50-udev-default.rules.in: set correct group for mediaX/cecX (#5921) (diff) | |
download | systemd-87057e244b4d2e723dc98b2b3cef1901c155f005.tar.gz systemd-87057e244b4d2e723dc98b2b3cef1901c155f005.tar.bz2 systemd-87057e244b4d2e723dc98b2b3cef1901c155f005.zip |
resolved: support libidn2 in addition to libidn
libidn2 2.0.0 supports IDNA2008, in contrast to libidn which supports IDNA2003.
https://bugzilla.redhat.com/show_bug.cgi?id=1449145
From that bug report:
Internationalized domain names exist for quite some time (IDNA2003), although
the protocols describing them have evolved in an incompatible way (IDNA2008).
These incompatibilities will prevent applications written for IDNA2003 to
access certain problematic domain names defined with IDNA2008, e.g., faß.de is
translated to domain xn--fa-hia.de with IDNA2008, while in IDNA2003 it is
translated to fass.de domain. That not only causes incompatibility problems,
but may be used as an attack vector to redirect users to different web sites.
v2:
- keep libidn support
- require libidn2 >= 2.0.0
v3:
- keep dns_name_apply_idna caller dumb, and keep the #ifdefs inside of the
function.
- use both ±IDN and ±IDN2 in the version string
Diffstat (limited to 'README')
-rw-r--r-- | README | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -142,7 +142,7 @@ REQUIREMENTS: libqrencode (optional) libmicrohttpd (optional) libpython (optional) - libidn (optional) + libidn2 or libidn (optional) elfutils >= 158 (optional) make, gcc, and similar tools |