Bug 1449140 - loudmouth: switch to libidn2
Summary: loudmouth: switch to libidn2
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: loudmouth
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: fedora28-switch-to-idna2008
TreeView+ depends on / blocked
 
Reported: 2017-05-09 09:38 UTC by Nikos Mavrogiannopoulos
Modified: 2018-11-30 23:10 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 23:10:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Nikos Mavrogiannopoulos 2017-05-09 09:38:00 UTC
Description of problem:
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.

The change is about deprecating libidn, which supports IDNA2003, and switch all applications using libidn, to libidn2 2.0.0, which supports IDNA2008. The switch should be transparent as the libidn2 library is API compatible. See instructions at:
https://libidn.gitlab.io/libidn2/manual/libidn2.html#Converting-from-libidn


This is part of the IDNA2008 change:
https://fedoraproject.org/wiki/Changes/IDNA2008

If upstream is not aware of that change please involve them on the process.

Comment 1 Jan Kurik 2017-08-15 07:51:34 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

Comment 2 Nikos Mavrogiannopoulos 2018-10-11 07:09:28 UTC
Pavel is that already fixed?

Comment 3 Pavel Zhukov 2018-10-11 07:13:07 UTC
(In reply to Nikos Mavrogiannopoulos from comment #2)
> Pavel is that already fixed?

I don't maintain loudmouth anymore. Please ask @pbrobinson

Comment 4 Peter Robinson 2018-10-11 09:25:18 UTC
No it's not, and I wonder how I got ended up landed with maintaining this. Ultimately this is not a packaging question, it needs to be reported upstream and when it's fixed by the developers we will get it in the form of a new version.

It's also easy enough to query whether it's fixed by checking the library it's linked against:

rpm -qR loudmouth  |grep idn
libidn.so.12()(64bit)
libidn.so.12(LIBIDN_1.0)(64bit)

Did you file a bug with upstream?

Comment 5 Nikos Mavrogiannopoulos 2018-10-11 09:35:25 UTC
No, if upstream is not aware of that change please notify them and involve them on the process.

Comment 6 Pavel Zhukov 2018-10-11 09:47:48 UTC
(In reply to Peter Robinson from comment #4)
> No it's not, and I wonder how I got ended up landed with maintaining this.
I've been surprised as well. I took ownership few years ago because of mcabber then someone (don't remember the name) took it from me and now I can see you as main admin in pagure :)

Comment 7 Ben Cotton 2018-11-27 14:06:17 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Ben Cotton 2018-11-30 23:10:08 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.