what the difference may be?
-Original Message-
From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf Of Fili, Tom
Sent: Friday, September 27, 2013 2:14 PM
To: openssl-users@openssl.org
Subject: RE: CAPI and Private keys
My mistake. I was looking at Common
rg]
On Behalf Of Dr. Stephen Henson
Sent: Thursday, September 26, 2013 2:08 PM
To: openssl-users@openssl.org
Subject: Re: CAPI and Private keys
On Thu, Sep 26, 2013, Fili, Tom wrote:
> Hmmm...ok. Is it possible that in some cases passing the subject to
> ENGINE_load_private_key is the incorrect
On Thu, Sep 26, 2013, Fili, Tom wrote:
> Hmmm...ok. Is it possible that in some cases passing the subject to
> ENGINE_load_private_key is the incorrect thing to do?
>
> What I'm doing seems pretty simple but in some cases I get key/value mismatch
> errors.
>
> I get the PCCERT_CONTEXT from the
: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf Of Dr. Stephen Henson
Sent: Thursday, September 26, 2013 6:53 AM
To: openssl-users@openssl.org
Subject: Re: CAPI and Private keys
On Wed, Sep 25, 2013, Fili, Tom wrote:
> I'm using the capi API to access
On Wed, Sep 25, 2013, Fili, Tom wrote:
> I'm using the capi API to access certificates in the Windows Cert Store. I'm
> using the following to get access to the private key
>
> EVP_PKEY *key = ENGINE_load_private_key(e, subject, 0, 0);
>
> This seems to work as far as I can tell. Even if the ce
I'm using the capi API to access certificates in the Windows Cert Store. I'm
using the following to get access to the private key
EVP_PKEY *key = ENGINE_load_private_key(e, subject, 0, 0);
This seems to work as far as I can tell. Even if the certificate requires a
password the OS prompts the us
