Closed
Bug 96162
Opened 24 years ago
Closed 24 years ago
"In PKCS11SecureRandom constructor" println
Categories
(JSS Graveyard :: Library, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
3.1.1
People
(Reporter: jamie-bugzilla, Assigned: jamie-bugzilla)
Details
There is a trace statement printed to stdout in the PKCS11SecureRandom constructor.
|
Assignee | |
Comment 1•24 years ago
|
||
This is only a problem in one place. Michelle can workaround as follows:
Instead of calling:
SecureRandom rng = SecureRandom.getInstance("pkcs11prng");
call:
JSSSecureRandom rng = CryptoManager.getSecureRNG();
JSSSecureRandom supports the nextByte() method, just like SecureRandom.
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 2•24 years ago
|
||
This is already fixed on the trunk, but it should be fixed for 3.1.1 as well.
Target Milestone: --- → 3.1.1
|
|
Assignee | |
Comment 3•24 years ago
|
||
Fixed on JSS_3_1_BRANCH.
/cvsroot/mozilla/security/jss/org/mozilla/jss/provider/PKCS11SecureRandom.java,v
<-- PKCS11SecureRandom.java
new revision: 1.2.2.1; previous revision: 1.2
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•