Open drbrandus opened 6 years ago
Let me check that ... Maybe I can destroy the object in a safe way to prevent that caching behavior.
In my opinion is that a "bug" from the MS .Net cryptographic functions itself.
The key iteself will be encrypted by the envelopedCms.Decrypt
and the DecryptMsg
function. There is no object cached within the key manager.
I've to look deeper in to the "private key handling" from the .Net/Windows side.
The smart card PIN should not be cached; leaving the smart card in the reader, after the first successful unlock, the DB can be unlocked simply selecting the P7Mkey file and the PIN is not asked again.