Closed
Bug 1317981
Opened 8 years ago
Closed 8 years ago
Fix a few places in certutil/crlutil/cmsutil that fail to use the provided password parameter
Categories
(NSS :: Tools, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
3.28
People
(Reporter: KaiE, Assigned: KaiE)
Details
Attachments
(1 file)
6.36 KB,
patch
|
rrelyea
:
review+
|
Details | Diff | Splinter Review |
A few scenarios of certutil/crlutil/cmsutil don't pass on the password parameter, so the tools are unnecessarily stuck and prompt for a password.
Assignee | ||
Comment 1•8 years ago
|
||
Attachment #8811251 -
Flags: review?(rrelyea)
Assignee | ||
Comment 2•8 years ago
|
||
It would be good to get this correctness fix into 3.28
Blocks: 1305970
Target Milestone: --- → 3.28
Assignee | ||
Updated•8 years ago
|
Flags: needinfo?(rrelyea)
Comment 3•8 years ago
|
||
Comment on attachment 8811251 [details] [diff] [review]
1317981-v1b.patch
Review of attachment 8811251 [details] [diff] [review]:
-----------------------------------------------------------------
::: cmd/smimetools/cmsutil.c
@@ +472,5 @@
> if (cms_verbose) {
> fprintf(stderr,
> "Created CMS message, added signed data w/ signerinfo\n");
> }
> + signerinfo->cmsg->pwfn_arg = pwcb_arg;
I think there may be a function that sets this, but this should be fine.
::: lib/smime/cmssigdata.c
@@ +726,5 @@
> }
> }
> + if (sigd->cmsg) {
> + pwarg = sigd->cmsg->pwfn_arg;
> + }
I think there may be a function that gets this, but again, this is fine.
Attachment #8811251 -
Flags: review?(rrelyea) → review+
Assignee | ||
Comment 4•8 years ago
|
||
I couldn't find smime functions that "return.*pfwn_arg".
I could find CMS message encoding functions that change the pwfn_arg of a message, but I couldn't find anything for the signer-info struct.
Flags: needinfo?(rrelyea)
Assignee | ||
Comment 5•8 years ago
|
||
Landed into NSS trunk:
https://hg.mozilla.org/projects/nss/rev/8e8ded73dca1
and also into NSS 3.28 branch:
https://hg.mozilla.org/projects/nss/rev/b09fe3c22b24
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•