We have the MS CAPI engine in openssl now.
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@open
Alon Bar-Lev wrote:
SNIP
> There is also an issue of resources prompt (passphrase, token) and a
> small issue of object serialization in engine interface.
If I remember well, smart card proprietary software will ask for
password when is necessary.
This should be part of engine API as well... S
On 7/1/07, Roumen Petrov <[EMAIL PROTECTED]> wrote:
> This is nice, although I don't see any real use case for this engine,
> as you require the user to manually export information from CryptoAPI
> store into files before the engine could be used.
There isn't such requirement.
Where? I guess yo
Please find answers in quoted text.
Alon Bar-Lev wrote:
Hello,
This is nice, although I don't see any real use case for this engine,
as you require the user to manually export information from CryptoAPI
store into files before the engine could be used.
There isn't such requirement.
I think O
Hello,
This is nice, although I don't see any real use case for this engine,
as you require the user to manually export information from CryptoAPI
store into files before the engine could be used.
I think OpenSSL engine (generic) should allow to expose certificate
store, this will allow engines
Please find attached file "openssl-mscrypto-20070625.tar.gz" with
openssl engine that can use keys from windows key-store. The engine can
work with external keys too.
Source is for openssl version 0.9.8 and mingw build require openssl
source with mingw patch for 0.9.8 from request #1552 ( see
