Open
Bug 305019
Opened 19 years ago
Updated 2 years ago
crmf: CRMFPOPOSigningKeyInputTemplate does not match to underlying structure
Categories
(NSS :: Libraries, defect, P3)
Tracking
(Not tracked)
NEW
People
(Reporter: alvolkov.bgs, Unassigned)
Details
here is one more template:
It from nss/lib/crmf/crmftmpl.c: 173
const SEC_ASN1Template CRMFPOPOSigningKeyInputTemplate[] = {
{ SEC_ASN1_SEQUENCE, 0, NULL,sizeof(CRMFPOPOSigningKeyInput) },
{ SEC_ASN1_OPTIONAL | SEC_ASN1_CONSTRUCTED |
SEC_ASN1_CONTEXT_SPECIFIC | 0,
offsetof(CRMFPOPOSigningKeyInput, authInfo.sender) },
{ SEC_ASN1_BIT_STRING | SEC_ASN1_OPTIONAL | 1,
offsetof (CRMFPOPOSigningKeyInput, authInfo.publicKeyMAC) },
{ SEC_ASN1_INLINE | SEC_ASN1_XTRN,
offsetof(CRMFPOPOSigningKeyInput, publicKey),
SEC_ASN1_SUB(CERT_SubjectPublicKeyInfoTemplate) },
{ 0 }
};
The corresponded structure is located at
nss/lib/crmf/crmfit.h:164
struct CRMFPOPOSigningKeyInputStr {
/* ASN1 must have only one of the next 2 options */
union {
SECItem sender; /*General Name*/
CRMFPKMACValue *publicKeyMAC;
}authInfo;
CERTSubjectPublicKeyInfo publicKey;
};
This template and so is the structure is not used throughout the code. I'm
puting this bug for the record to keep track of incorrect templates in nss.| Reporter | ||
Updated•19 years ago
|
Assignee: wtchang → alexei.volkov.bugs
Updated•19 years ago
|
QA Contact: jason.m.reid → libraries
Comment 2•19 years ago
|
||
http://lxr.mozilla.org/security/search?string=CRMFPOPOSigningKeyInput shows that the template is dead code. Let's just delete it from the source. The struct that goes with it seems to be used in some places, but maybe they're all dead code?
| Reporter | ||
Updated•18 years ago
|
Priority: -- → P3
Target Milestone: --- → 3.12
Comment 3•16 years ago
|
||
Unsetting target milestone in unresolved bugs whose targets have passed.
Target Milestone: 3.12 → ---
Updated•2 years ago
|
Severity: normal → S3
Comment 4•2 years ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Assignee: alvolkov.bgs → nobody
You need to log in
before you can comment on or make changes to this bug.
Description
•