New version of the libidn2 patch

[Florian Weimer]

On 03/15/2018 11:03 PM, Florian Weimer wrote:
> For some reason, libidn2 does not fail the conversion, but uses the 
> replacement character '?' for unencodable characters.  This will have to 
> be fixed in libidn2 eventually.

This has now been fixed in upstream libidn2.

I used to the fixed libidn2 to iron out a few more issues and adjusted 
the tests.  In particular, libidn2 decoding failures (for getnameinfo 
and canonical DNS names) return the punycode name to the application. 
This seems more future-proof than outright failing name resolution just 
because there's another IDNA standard.

I would welcome review of the libidn module removal parts of the patch. 
I'm confident that the DNS side is quite solid now, and would commit 
that part with my network subsystem maintainer head.

Thanks,
Florian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: idna-9999.patch
Type: text/x-patch
Size: 993776 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20180401/05d90e0b/attachment.bin>