Closed Bug 363721 Opened 19 years ago Closed 19 years ago

InvalidAlgorithmParameterException: RC2/CBC/NoPadding while decoding a PFX file

Categories

(JSS Graveyard :: Library, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 239809

People

(Reporter: wprice, Assigned: neil.williams)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727) Build Identifier: JSS4 I am getting the error: java.security.InvalidAlgorithmParameterException: RC2/CBC/NoPadding I am essentially using the code from the main program at: http://lxr.mozilla.org/security/source/security/jss/org/mozilla/jss/pkcs12/PFX.java The error is occuring at line 377 where the program attempts to get/decrypt the 2nd of 2 SafeContents. This SafeContents is encrypted with the pbeWithSHAAnd40BitRC2-CBC. The problem seems to occur with both JSS34 and JSS4. The problem has occurred with p12 files generated from NS 4.76, IE6, and another toolkit. I'd prefer to not provide the specific p12 files because of sensitivity to identifiers contained in the certificates. Reproducible: Always Steps to Reproduce: 1. Run the program from the referenced URL against an available pfx file. 2. 3. Actual Results: The program aborts with the described error message on line 377 while attempting to access the 2nd of 2 SafeContents Expected Results: Program should have successfully decrypted the SafeContents
Bill has sent us sample .p12 file with which the problem can be reproduced. Neil Williams has confirmed the bug with that p12 file, and is now working on this bug. Neil wrote: "Pk12util does not have a problem importing both certs in [the p12 file] so it's definitely a JSS bug." So I'm marking this bug confirmed.
Assignee: glen.beasley → neil.williams
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: libraries
Version: unspecified → 4.0
This bug looks like a duplicate of Bug 239809. Bill please confirm that (or refute it). Thanks.
(In reply to comment #2) > This bug looks like a duplicate of Bug 239809. > Bill please confirm that (or refute it). Thanks. Certainly looks like the same problem.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.