encryption - HSM - cryptoki - opening sessions overhead -


I have a question about sessions with HSM.

I know that if there is an overhead, you will start and finalize the Cryptoki API for each file, which you want to encrypt / decrypt.

My questions are,

  1. Is there an overhead in opening and closing a person session for each file, you want to encrypt / decrypt. (C_inilize / c_finelize)

  2. In addition to affecting the display, how many sessions can be the maximum number of simultaneous HSM?

  3. Is the best method for processing individual files or opening a session and opening and closing sessions for processing multiple files and then closing the best way to session ?

thanks

First of all, the normal form There are very detailed documentation from threads, applications and sessions about observation.

Secondly, this depends on your HSM Hardwa again and how does PKCS # 11 module implementation represent your PKCS # 11 provider slot? Do you use the same key all the time? What are the authentication mechanisms for the key?

  1. How to use C_Initialize (and C_Finalize) in the details of PKCS # 11 on a large scale
  2. Number of sessions PKCS # 11 implementation, see CK_TOKEN_INFO in ulMaxSessionCount < / Li>

Try with a session Are you sure your handicap will manage the session?


Comments

Popular posts from this blog

windows - Heroku throws SQLITE3 Read only exception -

lex - Building a lexical Analyzer in Java -

python - rename keys in a dictionary -