You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m using the SignServer Community Edition and have observed that the HSM is not being called for every signing request. Despite this, the signed data is still returned correctly to the client.
Could someone clarify what mechanism SignServer uses in this scenario? Is it caching key handles, using session-based signing, or applying some other optimization?
Additionally, is this behavior considered secure and aligned with best practices for cryptographic key usage?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I’m using the SignServer Community Edition and have observed that the HSM is not being called for every signing request. Despite this, the signed data is still returned correctly to the client.
Could someone clarify what mechanism SignServer uses in this scenario? Is it caching key handles, using session-based signing, or applying some other optimization?
Additionally, is this behavior considered secure and aligned with best practices for cryptographic key usage?
Beta Was this translation helpful? Give feedback.
All reactions