Activity for tjadm
-
tjadm modified a comment on discussion Technical Topics
Thank you very much for your information! I get VeraCrypt::SecurityToken::InitLibrary:534 And yes, it is the dynamic code generation issue. It is the middleware for a Pinpad to store keyfile(s).
-
Thank you very much for your information! I get VeraCrypt::SecurityToken::InitLibrary:534 And yes, it is the dynamic code generation issue. It is the middleware for a USB Chipdrive Pinpad to store keyfile(s). The idea is to use a keyfile that is locked away by a PIN which (hopefully) cannot be accessed by a keylogger. If I may ask in case you know: is there any recommendable middleware for use with a pinpad? (Currently used Cards are Atos CardOS V4.4) Of course I can send the DLL in question if you...
-
Thank you very much for your information! I get VeraCrypt::SecurityToken::InitLibrary:534 And yes, it is the dynamic code generation issue. It is the middleware for a USB Chipdrive Pinpad to store keyfile(s). The idea is to use a keyfile that is locked away by a PIN which (hopefully) cannot be accessed by a keylogger. If I may ask in case you know: is there any recommendable middleware for use with a pinpad? (Currently used Cards are Atos CardOS V4.4) I added the DLL if you are interested (i hope...
-
Thank you very much for your information! I get VeraCrypt::SecurityToken::InitLibrary:534 And yes, it is the dynamic code generation issue. It is the middleware for a USB Chipdrive Pinpad to store keyfile(s). The idea is to use a keyfile that is locked away by a PIN which (hopefully) cannot be accessed by a keylogger.
-
I get VeraCrypt::SecurityToken::InitLibrary:534 I hope that helps. It is the middleware for a USB Chipdrive Pinpad to store keyfile(s). And yes, it is the dynamic code generation issue.
-
I get VeraCrypt::SecurityToken::InitLibrary:534 I hope that helps. It is the middleware for a USB Chipdrive Pinpad to store keyfile(s). And yes, it is the dynamic code generation issue.
-
I get VeraCrypt::SecurityToken::InitLibrary:534 I hope that helps. It is the middleware for a USB Chipdrive Pinpad to store keyfile(s).
-
I don't know if my question is at the correct position here, but: after updating to 1.26.x i have no more possibility to use tokens. I opened a new Thread in technical topics, I think that works better.
-
After updating to 1.26.x i have no more possibility to use tokens. The version of the PKCS#11 library i used before (a file called cmP1164.dll, part of the Charismathics Smart Security Interface PKCS#11 Module) is no longer accepted. If I install an older version of VC (same Windows version) everything is fine.
-
I don't know if my question is at the correct position here, but: after updating to 1.26.x i have no more possibility to use tokens. The version of the PKCS#11 library i used before (a file called cmP1164.dll, part of the Charismathics Smart Security Interface PKCS#11 Module) is no longer accepted. If i install an older version of VC (same Windows version) everything is fine. Thanks for your ideas.
1