RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1674201 - Rebase of libidn2 to 2.2.0
Summary: Rebase of libidn2 to 2.2.0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libidn2
Version: 8.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: Miroslav Lichvar
QA Contact: Robin Hack
URL:
Whiteboard:
Depends On: 1674002 1674023
Blocks: CVE-2019-18224
TreeView+ depends on / blocked
 
Reported: 2019-02-09 19:30 UTC by Robert Scheck
Modified: 2020-11-14 13:10 UTC (History)
5 users (show)

Fixed In Version: libidn2-2.2.0-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 22:28:50 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3621 0 None None None 2019-11-05 22:28:55 UTC

Description Robert Scheck 2019-02-09 19:30:18 UTC 
Rebase of libidn2 to 2.1.1a (or backport fix), see bug #1674023 in general.
Comment 3 Tomáš Hozza 2019-03-05 08:54:53 UTC 
Hello Robert.

Thank you for taking the time to report this issue to us. We appreciate the feedback and use reports such as this one to guide our efforts at improving our products. That being said, this bug tracking system is not a mechanism for requesting support, and we are not able to guarantee the timeliness or suitability of a resolution.

If this issue is critical or in any way time sensitive, please raise a ticket through the regular Red Hat support channels to ensure it receives the proper attention and prioritization to assure a timely resolution. 

For information on how to contact the Red Hat production support team, please visit:
    https://access.redhat.com/support
Comment 4 Miroslav Lichvar 2019-06-06 12:43:10 UTC 
In the meantime there was a 2.2.0 release. It looks like bugfix release, with no new features. We should rebase to that.
Comment 5 Florian Weimer 2019-06-06 12:47:17 UTC 
(In reply to Miroslav Lichvar from comment #4)
> In the meantime there was a 2.2.0 release. It looks like bugfix release,
> with no new features. We should rebase to that.

Yes, libidn2 2.2.0 would keep the glibc testsuite clean.
Comment 11 Robert Scheck 2019-10-24 00:25:02 UTC 
Adressing CVE-2019-18224 might be another good reason for a rebase.
Comment 12 Tomáš Hozza 2019-10-24 10:08:35 UTC 
(In reply to Robert Scheck from comment #11)
> Adressing CVE-2019-18224 might be another good reason for a rebase.

The rebase is already planned for 8.1.0.
Comment 14 errata-xmlrpc 2019-11-05 22:28:50 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:3621
Note You need to log in before you can comment on or make changes to this bug.