Skip Menu |
Report information
The Basics
Id: 45806
Status: resolved
Priority: 0/
Queue: bind9-public

Bug Information
Version Fixed: 9.9.12, 9.10.7, 9.11.3, 9.12.0
Version Found: 9.9.3
Versions Affected: (no value)
Versions Planned: (no value)
Priority: P2 Normal
Severity: S2 Normal
CVSS Score: (no value)
CVE ID: (no value)
Component: BIND Utilities
Area: bug

Dates
Created:Fri, 18 Aug 2017 07:22:21 -0400
Updated:Mon, 21 Aug 2017 04:15:55 -0400
Closed:Mon, 21 Aug 2017 04:15:55 -0400



This bug tracker is no longer active.

Please go to our Gitlab to submit issues (both feature requests and bug reports) for active projects maintained by Internet Systems Consortium (ISC).

Due to security and confidentiality requirements, full access is limited to the primary maintainers.

To: bind9-public@isc.org
From: michal@isc.org
Subject: dnssec-settime incorrectly calculates dates for a successor key
Date: Fri, 18 Aug 2017 11:22:20 +0000
Commit c8803902d6e (included in BIND 9.9.3 and all further releases) broke calculation of publication and activation dates for a successor key (-S). Depending on dates set for the predecessor key, this may either cause a bogus fatal error to be reported or invalid dates to be set for the successor key.
Proposed fix is in rt45806, along with a minor documentation addendum and an error message tweak. Please review.
Looks good.
4685. [bug] dnssec-settime incorrectly calculated publication and activation dates for a successor key. [RT #45806] 9.9.12, 9.10.7, 9.11.3, 9.12.0