[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Failure with libidn2 on OpenBSD.

From: Tim Rühsen
Subject: Re: Failure with libidn2 on OpenBSD.
Date: Sun, 5 Apr 2020 21:40:22 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0

On 05.04.20 20:05, Alfred M. Szmidt wrote:
>    > since Simon Josefsson and Tim Rühsen are both involved in libidn2,
>    > this bug is doubly relevant here.
>    The bug is more relevant because Simon and I are involved in libidn2 ?
>    I don't understand - could could explain ?
> I think Mats-Erik simply meant that you/Simon might know something
> about it.  Thank you for adding help-libidn to the CC.
>    > which is to be expected of an IPv6 address. Similarly, the 
> OpenBSD+libidn2
>    > call transforms the legal "::ffff:" for the corrupted 
> "ffff127.0.0.1".
>    > 
>    > Thus the compatibility call idna_to_ascii_lz() in libidn2 strips off 
> every colon,
>    > when executed on OpenBSD but not on OpenIndiana. Explanation? Resolution?
>    > I get two failed tests with OpenBSD, but none with OpenIndiana!
>    The resolution is to update libidn2 to 2.3.0. 
> That isn't always possible or desirable, should we add a hack to
> handle this for older versions of libidn2?

You can always backport the relevant commits. But that needs some
expertise and may easily introduce other kinds of bugs.

Before I can help further, could you please give me the version of the
OpenBSD's libidn2 ?

And just for the record:

NEWS for the latest version:
* Version 2.3.0 (released 2019-11-14)

** Mitre has assigned CVE-2019-12290 which was fixed by
   the roundtrip feature introduced in 2.2.0 (commit 241e8f48)

** Update the data tables from Unicode 6.3.0 to Unicode 11.0

Regards, Tim

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]