[Bug 49144] Opening a PFX certificate in a dotnet application using X509Certificate2

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=49144

--- Comment #7 from Hans Leidekker <hans at meelstraat.net> ---
(In reply to petrov_lv from comment #6)
> Result (DEBUG+crypto_rsa4096_key.log):
> > HasPrivateKey: False
> > IssuerName:    C=RU, S=Test state, O=test org., OU=test unit, CN=Test User
> > SubjectName:   C=RU, S=Test state, O=test org., OU=test unit, CN=Test User
> 
> * NO exception is thrown
> * private key NOT loaded
> 
> "Windows" output:
> > HasPrivateKey: True
> > IssuerName:    C=RU, S=Test state, O=test org., OU=test unit, CN=Test User
> > SubjectName:   C=RU, S=Test state, O=test org., OU=test unit, CN=Test User
> 
> A private key is required in the main application. Maybe I should create a
> new report?

It's a different issue but DSA support is already covered in other bug reports,
so we might as well continue here.

It's looking for CERT_KEY_PROV_INFO_PROP_ID on the imported cert, which isn't
set.

-- 
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.