Crash in pteidmdrv64.dll

[scofieldwz]

Our application create digital signatue using Windows Crypto API. When I use a previous generation ID card, everything works fine. But when I select a new ID card, a pin code dialog shows up:

I didn't type in the pin code immediately, after a while our app crashed. I debug the dump file and find something about pteidmdrv64.dll in the stacktrace:

Without the symbol file of PTEID sdk, I cannot find out what is wrong with our app. Hope official developers can give me some clues.

[agrr]

Hello,

PTEID SDK can store useful debugging information in log files located at C:\Program Files\Portugal Identity Card\log.

But first make sure that registry value named log_level is set to the string "debug" in the following key: HKEY_CURRENT_USER\SOFTWARE\PTEID\logging

After reproducing your issue again please share the pteidmdrv.log and .PTEID_*.log files created in the log directory.

Another important info for us: what's your Windows OS version ?

[scofieldwz]

Glad to hear from you!

My Windows OS version is Windows 10 Home (19045.5965).

I've put the log fils in the attachment.

.PTEID_0.log

pteidmdrv.log

[agrr]

Hello @scofieldwz

We couldn't reproduce your issue with a test application that should be similar to your usecase. Besides, your log files don't show any erroneous behaviour.

On Windows 10 our application has the following workflow:
it calls CertFindCertificateInStore to search for the registered Portugal eID card certificate.
The search parameter we use is the Issuer string "EC de Assinatura Digital", all the certificates of our PT eID cards have this issuer CA.
Then it calls the CryptoAPI function CryptSignMessage() using the previously found certificate context as the pSigningCert member of the parameter of type CRYPT_SIGN_MESSAGE_PARA.
I can run the program and generate a PKCS#7 signature using cards of the old generation (RSA signature) or new generation (ECDSA signature).

We've also tested other CryptoAPI test cases and applications without finding any issues.

The stacktrace you shared from the Visual Studio debugger indicates a crash because IMO the heap management functions in Windows (ntdll) found something wrong in its internal data structures, I think this is a class of errors that's normally called heap corruption, and it can be hard to debug. It may be caused by an invalid/out of bounds memory write in your application code that is only "detected" later when our component pteidmdrv64.dll calls a deallocation function.

[scofieldwz]

Hello @agrr , I finally found that it has something to do with mimalloc . We brought in mimalloc to improve the performence of our app. Everything works fine after I disable it.
The crash happened when pteidmdrv64.dll was calling HeapFree(). It seems that the corresponding Heap allocation was redirected by mimalloc while HeapFree() was not. One of my colleagues used to encounter this problem, and his recommendation is: always use the C-runtime library as a DLL (using the /MD or /MDd switch). I wonder if the pteidmdrv64.dll in C:\Windows\System32 is compiled that way. We hope PTEID developers can find a way to solve this problem so that we don't need to create a new process to finish digital signature.