On Wed May 20 08:30:49 2026 +0000, Hans Leidekker wrote:
I don't know if this is right, this patch only changes the code to use the appropriate union field. I looked into this in the context of this bug: https://bugs.winehq.org/show_bug.cgi?id=59757 Does 'dotnet restore' also pass a CERT_KEY_CONTEXT instead of a NCRYPT_KEY_HANDLE by any chance? The dotnet runtime passes an NCRYPT_KEY_HANDLE (from a SafeNCryptKeyHandle) in pvData to this function with CERT_NCRYPT_KEY_HANDLE_PROP_ID.
https://github.com/dotnet/runtime/blob/60629d14374c56f1cb51819049ad1fa529307... You can test it. Whatever you pass in pvData is what will be put into the cert parameter and will be read back. If you call this function with pvData=0xDEADBEEF it'll happily put that in the parameter. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10948#note_140917