Closed
Bug 328233
Opened 18 years ago
Closed 18 years ago
HMACTest.java on HP-UX fails with NPE
Categories
(JSS Graveyard :: Tests, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
4.2.3
People
(Reporter: Sandeep.Konchady, Assigned: Sandeep.Konchady)
Details
Attachments
(1 file)
2.11 KB,
patch
|
alvolkov.bgs
:
superreview+
|
Details | Diff | Splinter Review |
HMACTest.java fails with NPE on HP-UX. This is because the java.vendor is checked for IBM or Sun. But in case of HP-UX, the provider is Hewlett-Packard Co. Need to change the clause to either use IBM JCE in case of IBM JDK or Sun JCE in case of all other JDKs. java.lang.NullPointerException at org.mozilla.jss.tests.HMACTest.doHMAC(HMACTest.java:72) at org.mozilla.jss.tests.HMACTest.main(HMACTest.java:130)
Assignee | ||
Comment 1•18 years ago
|
||
Setting the macJCE to either IBMJCE or SunJCE. if ( javaVendorName.equals("IBM Corporation") ) { macJCE = Mac.getInstance(alg, "IBMJCE"); } else { macJCE = Mac.getInstance(alg, "SunJCE"); }
Status: NEW → ASSIGNED
Target Milestone: --- → 4.2.3
Assignee | ||
Updated•18 years ago
|
Summary: HMACTest.java on HP-US fails with NPE → HMACTest.java on HP-UX fails with NPE
Assignee | ||
Comment 2•18 years ago
|
||
Test Result: 39 bytes to be digested main: jss library loaded The Java version is: 1.4.2.05 MD2 digest output size is 16 SUN and Mozilla-JSS give same MD5 message digests SUN and Mozilla-JSS give same SHA-1 message digests SUN and Mozilla-JSS give same SHA-256 message digests SUN and Mozilla-JSS give same SHA-384 message digests SUN and Mozilla-JSS give same SHA-512 message digests JSSTEST_CASE 7 (Digesting): PASS
Attachment #212807 -
Flags: superreview?(alexei.volkov.bugs)
Updated•18 years ago
|
Attachment #212807 -
Flags: superreview?(alexei.volkov.bugs) → superreview+
Assignee | ||
Comment 3•18 years ago
|
||
/cvsroot/mozilla/security/jss/org/mozilla/jss/tests/HMACTest.java,v <-- HMACTest.java new revision: 1.3; previous revision: 1.2 done
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•