http://bugs.winehq.org/show_bug.cgi?id=60443 --- Comment #1 from mailtomendoza@gmail.com --- Created attachment 82337 --> http://bugs.winehq.org/attachment.cgi?id=82337 Suggested patch (tested on Wine 11.19, not upstream-ready) For reference, a minimal patch along these lines (P-256 only) that was tested here is attached: it sets Algorithm Name / Algorithm Group / ECCCurveName / SignatureLength on ECDSA_P256 key objects, imports BCRYPT_ECDSA_{PUBLIC,PRIVATE}_P256_MAGIC blobs through BCryptImportKeyPair(BCRYPT_ECDSA_P256_ALG_HANDLE), and FIXME-ignores the NCryptBufferDesc parameter list instead of failing. Observed with .NET Framework 4.8 on Wine 11.19: ECDsa.Create(ECCurve.NamedCurves.nistP256) works, but ExportParameters(), CertificateRequest.CreateSelfSigned() and anything copying the key fail with CryptographicException 0x80090027, because .NET queries "Algorithm Name" and then re-imports the key with NCryptImportKey(BCRYPT_ECCPRIVATE_BLOB, params = NCRYPTBUFFER_PKCS_KEY_NAME). It is a suggestion, not an upstream-ready patch: no P-384/P-521, no new tests, and ignoring the key-name parameter means a named key silently becomes ephemeral. Applies to wine-11.19 and current master; ncrypt conformance tests unchanged (i386 and x86_64). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.