Hello,

we're currently doing an implementation of NSS and one of our HSM's for a customer. So far this works perfectly fine. However the problem arrises if we try to disable the whole module or a particular slot using "modutil -disable...".

Short story, it seems to have no effect.

Long story, looking at the code PK11_UserDisableSlot seems to do what is expected to do. Also debugging on the low-level shows that secmod.db gets modified in order to reflect the change. But any consecutive "modutil -list..." is still displaying the slot as enabled. We also tried to modify the code so when a new module is added the SlotSructure defaults to slot->disabled = PR_TRUE. Which results in an "disabled" status while listing the module. Still, a "modutil -enable" seems to do the job codewise but the result ist the expected one. So the slot in this case remains disabled and does not get changed.

So whichever way we looked at it, we cant figure out what the problem here is.

Any suggestions are much appreciated.

Andreas Kroehnert
SafeNet UK Ltd.
Subject Matter Expert
Commercial Security Division
+44 (0)1276 608046 - office
+44 (0)7852 925958 - mobile
www.safenet-inc.com
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto

Reply via email to