22.04 idn -a domain.com idn: could not convert from ASCII to UTF-8
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libidn (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Kinetic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[ Impact ]
idn cannot handle non-ASCII characters
[ Test Plan ]
Existing state in 22.04:
$ echo ü | idn
idn: could not convert from ASCII to UTF-8
Fixed output:
$ echo ü | idn
xn--tda
[ Where problems could occur ]
The patch enables an extra autotools features, so the most likely problem is a build failure. Currently non-ASCII characters are entirely unhandled, so there's no risk of regression there, but this could potentially turn clean failures into crashes or incorrect output.
[Original report]
On Ubuntu 22.04 Jammy:
idn -a "xxx-tést.eu"
idn: could not convert from ASCII to UTF-8
And
idn -u "xn--xxx-
idn: could not convert from UTF-8 to ASCII
Expected:
Successfully conversion from ASCII to UTF-8
Ubuntu 20.04 / 18.04 it works fine
Also with idn2 from UTF-8 to ASCII works as expected how ever support lacks from ASCII to UTF-8
Description: Ubuntu 22.04 LTS
Release: 22.04
root@test:~# echo $LC_ALL
C.UTF-8
root@test:~# apt-cache policy idn
idn:
Installed: 1.38-4build1
Candidate: 1.38-4build1
Version table:
*** 1.38-4build1 500
500 https:/
100 /var/lib/
description: | updated |
Changed in libidn (Ubuntu Jammy): | |
status: | New → Confirmed |
Changed in libidn (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in libidn (Ubuntu Kinetic): | |
status: | New → Fix Released |
tags: |
added: verification-done-jammy removed: verification-needed-jammy |
For conversion backwards use idn2 -d domain.com
How ever it doesn't stop why it doesn't work for idn package it self