Force cache flush? about rust-cryptoki HOT 5 CLOSED

Note: Please don't block an 0.3.0 release on this point.

from rust-cryptoki.

Minor update: I've modified our code to test if finalizing and re-initializing works with cryptoki with the same benefit that I saw with the pkcs11 crate but I've run out of time for today and am not working tomorrow, so actual testing will have to wait until next week.

from rust-cryptoki.

I discovered that calling C_Finalize() and then C_Initialize() again would "flush" this cache and permit Krill to connect to the HSM without requiring a restart of Krill.

Hmmm, as far as I know, we call finalize on the open context when it's dropped, and so our "public" version of finalize just takes ownership of the context and drops it. Presumably what you'd need is a method that calls finalize while allowing the user to keep ownership of the context?

from rust-cryptoki.

Yes, previously I could call finalize and still have the context and call initialize on it again, now I cannot do that. I expect I can change my code to be able to create a whole new context instance but if it's a valid pattern to finalize and re-initialize and if it is valid per the PKCS#11 spec and it actually has real world value then an alternate model that permits ownership to be retained might be good to have.

Have you not run in to this same issue yourselves?

from rust-cryptoki.

@ionut-arm: I've tested my changes and it seems to work, thanks!

from rust-cryptoki.