Closed
Bug 67511
Opened 24 years ago
Closed 24 years ago
PK11_ConfigurePKCS11 is very strict on strings size
Categories
(NSS :: Libraries, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
3.3
People
(Reporter: julien.pierre, Assigned: rrelyea)
References
Details
When using that call to set the strings for tokens, etc.; the call only works if
the string is exactly of a certain length, and requires strings to be padded
with spaces.
For example we have to pass "internal " to the function
in order for the token name to be set right.
Subsequently, a PK11_GetTokenName(PK11_GetInternalSlot()) will return
"internal", without the spaces.
We have some logic in our server that needs to match passwords by token name,
and this has been causing us a lot of grief. I would like to see this function
fixed in the 3.2 RTM. The fix would be that it no longer requires padding
spaces, and accepts any strings up to the maximum size.
Updated•24 years ago
|
Assignee: wtc → relyea
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 1•24 years ago
|
||
Assigned the bug to Bob.
Updated•24 years ago
|
Priority: -- → P3
Target Milestone: --- → 3.3
Assignee | ||
Comment 3•24 years ago
|
||
Latest PKCS #11 checkings should fix this.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•