Closed
Bug 377542
Opened 17 years ago
Closed 17 years ago
Eliminate duplicate implementation of cert validity time checking
Categories
(NSS :: Libraries, enhancement, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
3.11.7
People
(Reporter: nelson, Assigned: nelson)
Details
Attachments
(1 file)
1.57 KB,
patch
|
neil.williams
:
review+
alvolkov.bgs
:
superreview+
|
Details | Diff | Splinter Review |
Sometime long before NSS 1.5 was released, a second function was written to determine if a certificate was in its validity period. The new function allowed the caller to specify the time that was to be checked against the cert's validity period (whereas the first function always tested against NOW). The second function also allowed the caller to specify whether or not to allow the validity time to be overridden with the timeOK flag in the CERTCertificate. A comment was added to the source for the original function, CERT_CertTimesValid, saying this: * WARNING - this function is depricated, and will go away in the near future. * It has been superseded by CERT_CheckCertValidTimes(). Over a decade later, both functions exist with their sightly different implementations. The attached patch eliminates the duplication of code, by reimplementing the older function as a call to the newer one.
Attachment #261584 -
Flags: superreview?(alexei.volkov.bugs)
Attachment #261584 -
Flags: review?(neil.williams)
Updated•17 years ago
|
Attachment #261584 -
Flags: review?(neil.williams) → review+
Updated•17 years ago
|
Attachment #261584 -
Flags: superreview?(alexei.volkov.bugs) → superreview+
Assignee | ||
Comment 1•17 years ago
|
||
Bug 377542. Eliminate duplicate implementation of cert validity time checking. r=neil.williams,alexei.volkov On trunk: Checking in certvfy.c; new revision: 1.51; previous revision: 1.50 On 3.11 branch: Checking in certvfy.c; new revision: 1.44.10.6; previous revision: 1.44.10.5
Status: NEW → RESOLVED
Closed: 17 years ago
Priority: -- → P3
Resolution: --- → FIXED
Target Milestone: 3.12 → 3.11.7
You need to log in
before you can comment on or make changes to this bug.
Description
•