Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 875981[details]
reproducer
+++ This bug was initially created as a clone of Bug #1077776 +++
Description of problem:
Recently I noticed communication on ldns-users list about error in ldns.
The error was causing ldns to randomly produce bad signs when using DSA
algorithm.
Version-Release number of selected component (if applicable):
ldns-1.6.16-6.fc20.x86_64
How reproducible:
randomly
Steps to Reproduce:
1. run the attached reproducer
Actual results:
reproducer exiting with "1"
Expected results:
reproducer exiting with "0"
Additional info:
mailing list communication:
https://open.nlnetlabs.nl/pipermail/ldns-users/2014-March/000728.html
As unbound used in RHEL-7 as validator for DNSSEC on Workstations feature
is linked against ldns, I think we should fix it, if possible.
No one is really using DSA for DNSSEC any. I would not worry about it too much.
http://secspider.cs.ucla.edu/stats.html
800 out of 1M DNSKEYs seems to be DSA - prob mostly legacy and test sites
So I wouldn't make this a high priority item
(In reply to Paul Wouters from comment #4)
> No one is really using DSA for DNSSEC any. I would not worry about it too
> much.
>
> http://secspider.cs.ucla.edu/stats.html
>
> 800 out of 1M DNSKEYs seems to be DSA - prob mostly legacy and test sites
>
> So I wouldn't make this a high priority item
I agree it is not high priority. This bug is more for tracking that the issue
is there and if possible, it can be easily fixed and tested.
Created automated test, which runs the reproducer
********************************
Old package:
ldns-1.6.16-7.el7.x86_64
:: [ FAIL ] :: Run test script (Expected 0, got 1)
********************************
New packge:
ldns-1.6.16-10.el7.x86_64
:: [ PASS ] :: Run test script (Expected 0, got 0)
Since the test Passed => verified
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://rhn.redhat.com/errata/RHBA-2016-2386.html