Report information
The Basics
Id:
45664
Status:
resolved
Priority:
Low/Low
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.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:
BIND Common
Area:
feature

Dates
Created:Tue, 01 Aug 2017 04:02:23 -0400
Updated:Wed, 02 Aug 2017 19:48:31 -0400
Closed:Wed, 02 Aug 2017 19:48:20 -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
Subject: isc_time_formattimestamp and friends are not thread safe.
From: marka@isc.org
Date: Mon, 31 Jul 2017 22:02:23 -1000
isc_time_formattimestamp calls localtime rather than localtime_r when threaded. there are similar issues for gmtime vs gmtime_r.
From: "Ray Bellis" <ray@isc.org>
Subject: Re: [ISC-Bugs #45664] isc_time_formattimestamp and friends are not thread safe.
To: bind9-public@isc.org
Date: Tue, 1 Aug 2017 09:10:05 +0100
On 01/08/2017 09:02, Mark Andrews via RT wrote: > isc_time_formattimestamp calls localtime rather than localtime_r when threaded. > there are similar issues for gmtime vs gmtime_r. While this is being looked at, I noticed that all three possible time strings are generated for every log entry even though only one will be used.
ready for review
4668. [bug] Use localtime_r and gmtime_r for thread safety. [RT #45664]