New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some HSMs could change the slot ID during operation #1309

cornelinux opened this Issue Nov 13, 2018 · 0 comments


None yet
1 participant

cornelinux commented Nov 13, 2018

Some HSMs (e.g. the LunaSA in HA setup) could change the Slot ID during operation (if one HSM node gets down in a HA setup)

In this case the following would happen:

  1. Open Sessions, that are bound to the slot ID will not work anymore. We immediately receive an error, despite the HA setup.
  2. The configuration would not work anymore. Slots could not be identified by the ID (which is a bit awkward, because this is the way, they are identified.)

If we want to cope with that, the following would have to happen:

  1. We would need to handle errors of a non present slot :-(
    Reinitialize, reconnect.
    but to do this
  2. we can not read the SlotID from the configuration.
    We could try to use the description (Not Unique!) of a slot, which we can iterate with
    1. C_GetSlotList
    2. C_GetSlotInfo
      The session still needs to be set up using the Slot ID again! :-(
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment