Open
Bug 677981
Opened 12 years ago
Updated 5 months ago
CERT_PKIXVerifyCert does not allow a self-signed cert to be used as its own trust anchor
Categories
(NSS :: Libraries, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: keeler, Unassigned)
Details
Attachments
(4 files, 4 obsolete files)
Can't use a CERTValInParam of type cert_pi_trustAnchors to set a self-signed certificate as a trust anchor, then use CERT_PKIXVerifyCert to verify that certificate (for things like expiration, bad signature, etc.) Results in SEC_ERROR_UNKNOWN_ISSUER.
![]() |
Reporter | |
Comment 1•12 years ago
|
||
![]() |
Reporter | |
Comment 2•12 years ago
|
||
![]() |
Reporter | |
Comment 4•12 years ago
|
||
revocation flags need to be specified for CERT_PKIXVerifyCert to work ( -> updated selfsigned.c)
Attachment #552144 -
Attachment is obsolete: true
![]() |
Reporter | |
Comment 5•12 years ago
|
||
proposed patch (if the certificate is self-signed (i.e. a root), temporarily set the basic constraints criterion's minimum path length to -2, indicating that the certificate must be an end-entity certificate).
![]() |
Reporter | |
Comment 6•12 years ago
|
||
Better patch (previous one was not at all the way to do it).
Attachment #552414 -
Attachment is obsolete: true
![]() |
Reporter | |
Comment 7•12 years ago
|
||
Using pointer equality for certs. Also, switching out the minimum path length argument only needs to happen in one location, not the two from before.
Attachment #553291 -
Attachment is obsolete: true
![]() |
Reporter | |
Updated•12 years ago
|
Attachment #553617 -
Flags: review?(bsmith)
![]() |
Reporter | |
Comment 8•10 years ago
|
||
Comment on attachment 553617 [details] [diff] [review] CERT_PKIXVerifyCert-selfsigned.patch Clearing review. If this patch even still applies, there's a good chance we're not going to be using libpkix, so we don't even need it.
Attachment #553617 -
Flags: review?(bsmith)
Comment 9•10 years ago
|
||
Keeler, we might still need libpkix for backwards compatibility. I would not throiw the effort away. However make sure you also check the certifiacte usages on the self signed case.
Updated•5 months ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•