Closed
Bug 510184
Opened 15 years ago
Closed 15 years ago
Crlutil failed to modify CRL because of the same timestamp.
Categories
(NSS :: Test, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
3.12.4
People
(Reporter: slavomir.katuscak+mozilla, Assigned: slavomir.katuscak+mozilla)
Details
Attachments
(1 file)
1.49 KB,
patch
|
alvolkov.bgs
:
review+
|
Details | Diff | Splinter Review |
chains.sh: Revoking certificate with SN 14 issued by CA1 crlutil -M -d CA1DB -n CA1 -f CA1DB/dbpasswd -o CA1.crl === Crlutil input data === update=20090813100004Z addcert 14 20090813100004Z === crlutil: fail to save CRL : New CRL is not later than the current one. chains.sh: #9022: Revocation: Revoking certificate with SN 14 issued by CA1 - FAILED Seems that CRL modification was done in the same second as CRL was created, that caused crlutil failure, existing code already contains 'sleep 1' command, but seems that this is not enough and in this case CRL creation, sleep 1 and CRL modify occurred within one second.
Assignee | ||
Comment 1•15 years ago
|
||
Attachment #394256 -
Flags: review?(alexei.volkov.bugs)
Assignee | ||
Updated•15 years ago
|
Summary: Crlutil failed to change CRL because of the same timestamp. → Crlutil failed to modify CRL because of the same timestamp.
Comment 2•15 years ago
|
||
Slavo, a simpler change would just change sleep 1 to sleep 2
Comment 3•15 years ago
|
||
An even better change would not sleep at all, and be able to increment the date programatically. But for an expedient fix , sleep 2 should work.
Updated•15 years ago
|
Attachment #394256 -
Flags: review?(alexei.volkov.bugs) → review+
Comment 4•15 years ago
|
||
Comment on attachment 394256 [details] [diff] [review] Patch. r=alexei
Assignee | ||
Comment 5•15 years ago
|
||
(In reply to comment #2) > Slavo, a simpler change would just change sleep 1 to sleep 2 This is also time optimalization, in some cases sleep would be completely skipped, so few seconds would be saved. (In reply to comment #3) > An even better change would not sleep at all, and be able to increment the date > programatically. But for an expedient fix , sleep 2 should work. Incrementing time without sleep could cause that we would have CRLs with update time in future.
Assignee | ||
Comment 6•15 years ago
|
||
Checking in chains.sh; /cvsroot/mozilla/security/nss/tests/chains/chains.sh,v <-- chains.sh new revision: 1.22; previous revision: 1.21 done
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•