Report information
The Basics
Id:
47042
Status:
resolved
Priority:
Medium/Medium
Queue:

People
Owner:
Nobody in particular
Cc:
AdminCc:

BugTracker
Version Fixed:
9.9.12, 9.9.12(sub), 9.10.7, 9.10.7(sub), 9.11.3, 9.12.1, 9.13.0
Version Found:
(no value)
Versions Affected:
(no value)
Versions Planned:
(no value)
Priority:
P2 Normal
Severity:
S2 Normal
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
(no value)
Area:
bug

Dates
Created:Tue, 23 Jan 2018 10:21:06 -0500
Updated:Tue, 23 Jan 2018 16:02:40 -0500
Closed:Tue, 23 Jan 2018 16:02:40 -0500



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.

From: "Petr Menšík" <pemensik@redhat.com>
Subject: Wrong timestamp is logged
To: bind9-bugs@isc.org
Date: Tue, 23 Jan 2018 16:21:00 +0100
Hello, I were just analyzing our BIND code to tell difference between "dnssec-loadkeys-interval" and "sig-validity-interval". I found a strange code that I believe logs incorrect timestamp. In lib/dns/zone.c:6125; set_key_expiry_warning is logging zone->refreshkeytime instead of zone->keywarntime it just changed. Unless it is non-obvious intention, I think this is just copy & paste error. Patch for master attached. Best Regards, Petr -- Petr Menšík Software Engineer Red Hat, http://www.redhat.com/ email: pemensik@redhat.com PGP: 65C6C973

Message body is not shown because sender requested not to inline it.

Thanks. 4874. [bug] Wrong time display when reporting new keywarntime. [RT #47042]