Bug 525556

Summary: ldns-signzone silently breaks zone signing (update to 1.6.1)
Product: [Fedora] Fedora EPEL Reporter: Noa Resare <noa>
Component: ldnsAssignee: Paul Wouters <pwouters>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: el5CC: pwouters
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-10-01 19:34:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Noa Resare 2009-09-24 20:10:24 UTC
Description of problem:
ldns-signzone in ldns-1.5.1 is broken in such a way that it silently generates invalid zone data. An unpleasant surprise when I moved my nameserver from a el4 box (where I had compiled my own updated ldns) to a vanilla el5 + epel.

According to DNSSEC spec all conforming dnsservers returns SERVFAIL on queries for data in the zones signed with ldns-1.5.1. so this is kind of serious.

Version-Release number of selected component (if applicable):
ldns-1.5.1-1.el5

How reproducible:
always

Steps to Reproduce:
1. generate two pairs of keys
2. sign a zone with those keys

  
Actual results:
the keytag of the key signing key is by one which results in a mismatch between the DNSKEY records in the signed zone and the DS records in the parent zone

Expected results:
matching keytag integers of DNSKEY and DS records, functioning zone validation

Additional info:
With an update to the current 1.6.1 release this problem is solved (no changes to the .spec file is needed except for the version bump). Some investigation points to changes in r2878 that landed somewehere before 1.6.0.

Comment 1 Noa Resare 2009-10-01 19:34:56 UTC
ldns-1.6.1-2.el5 made it's appearance in a yum update today. I hope that 'CURRENTRELEASE' is the right choice for closing this