67511 - PK11_ConfigurePKCS11 is very strict on strings size

Status: RESOLVED FIXED

(NSS :: Libraries, defect, P3)

Description

[Julien Pierre]

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.

Comment 1

[Wan-Teh Chang]

Assigned the bug to Bob.

Comment 2

[Robert Relyea]

*** Bug 58168 has been marked as a duplicate of this bug. ***

Comment 3

[Robert Relyea]

Latest PKCS #11 checkings should fix this.