Closed
Bug 438814
Opened 17 years ago
Closed 16 years ago
Testing CRL Distribution Points Extension - tests failed on Windows.
Categories
(NSS :: Tools, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
3.12.1
People
(Reporter: slavomir.katuscak+mozilla, Assigned: julien.pierre)
Details
Build: securitytip/20080611.1/nss-w2kp_WIN64/NSS-W2KP.1
Log:
certutil -d e:/security/securitytip/builds/20080611.1/nss-w2kp_WIN64/mozilla/tests_results/security/NSS-W2KP.1/cert_extensions -S -n TestExt -t u,u,u -o /tmp/cert -s CN=TestExt, E=TestExt@bogus.com, O=BOGUS NSS, L=Mountain View, ST=California, C=US -x -f ../tests.pw.2496 -z ../tests_noise.2496 -3
Enter value for the authKeyID extension [y/N]?
Enter value for the key identifier fields,enter to omit:
Select one of the following general name type:
2 - rfc822Name
3 - dnsName
5 - directoryName
7 - uniformResourceidentifier
8 - ipAddress
9 - registerID
Any other number to finish
Choice: >
Enter data:
Select one of the following general name type:
2 - rfc822Name
3 - dnsName
5 - directoryName
7 - uniformResourceidentifier
8 - ipAddress
9 - registerID
Any other number to finish
Choice: > Enter value for the authCertSerial field, enter to omit:
Is this a critical extension [y/N]?
Generating key. This may take a few moments...
certutil options:
y
3
test.com
214123
y
cert.sh: #429: Testing Certificate Authority Key Identifier Extension - PASSED
#################################################
certutil -d e:/security/securitytip/builds/20080611.1/nss-w2kp_WIN64/mozilla/tests_results/security/NSS-W2KP.1/cert_extensions -S -n TestExt -t u,u,u -o /tmp/cert -s CN=TestExt, E=TestExt@bogus.com, O=BOGUS NSS, L=Mountain View, ST=California, C=US -x -f ../tests.pw.2496 -z ../tests_noise.2496 -4
Enter the type of the distribution point name:
1 - Full Name
2 - Relative Name
Any other number to finish
Choice: >
Select one of the following general name type:
2 - rfc822Name
3 - dnsName
5 - directoryName
7 - uniformResourceidentifier
8 - ipAddress
9 - registerID
Any other number to finish
Choice: >
Enter data:
Select one of the following general name type:
2 - rfc822Name
3 - dnsName
5 - directoryName
7 - uniformResourceidentifier
8 - ipAddress
9 - registerID
Any other number to finish
Choice: >
Enter data:
Select one of the following general name type:
2 - rfc822Name
3 - dnsName
5 - directoryName
7 - uniformResourceidentifier
8 - ipAddress
9 - registerID
Any other number to finish
Choice: >
Enter data:
Select one of the following general name type:
2 - rfc822Name
3 - dnsName
5 - directoryName
7 - uniformResourceidentifier
8 - ipAddress
9 - registerID
Any other number to finish
Choice: >
Enter data:
Select one of the following general name type:
2 - rfc822Name
3 - dnsName
5 - directoryName
7 - uniformResourceidentifier
8 - ipAddress
9 - registerID
Any other number to finish
Choice: >
Select one of the following for the reason flags
0 - unused
1 - keyCompromise
2 - caCompromise
3 - affiliationChanged
4 - superseded
5 - cessationOfOperation
6 - certificateHold
Any other number to finish Choice: > Enter value for the CRL Issuer name:
Select one of the following general name type:
2 - rfc822Name
3 - dnsName
5 - directoryName
7 - uniformResourceidentifier
8 - ipAddress
9 - registerID
Any other number to finish
Choice: > Enter another value for the CRLDistributionPoint extension [y/N]?
Is this a critical extension [y/N]?
Generating key. This may take a few moments...
certutil options:
1
2
rfc822@name.tld
3
test.com
8
1.2.3.4
9
OID.0.2.213
10
0
10
n
n
e:\security\securitytip\builds\20080611.1\nss-w2kp_WIN64\mozilla\dist\WINNT5.2_DBG.OBJ\bin\certutil.exe: Could not find: TestExt
: security library: bad database.
cert.sh: #430: Testing CRL Distribution Points Extension (1) - FAILED
cert.sh ERROR: Testing CRL Distribution Points Extension failed 1
From log it seems that one test using TestExt passed, and next failed (also all next tests using TestExt failed).
This issue occurred only on this one machine and only in this one build.
Assignee | ||
Comment 1•16 years ago
|
||
I don't see this happening in the nightlies or tinderbox . It seems the issue may have been resolved by using different cert nicknames in the tests for each extension.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•