Viktor,
I would like to thank you very much.
The link to secure-messaging Git repos and your further explanations solved
all my problems.
I had to learn this pkcs11/iasecc in a short time but now I am able to sign
files with openssl / smime / engine_pkcs11 /opensc / iasecc card!
The produced sig
On Mon, Dec 5, 2011 at 12:53 PM, Mattes, David wrote:
> Hi Peter,
>
> I would love to see this functionality in the engine_pkcs11. We have
> applications that would benefit from this addition.
I should have a patch ready for submission in a couple of days. Not
much needs to be changed since th
On 12/6/2011 1:04 AM, Hunter William wrote:
>> Since the minidriver is being built within the Microsoft Crypto
>> framework, rather then using OpenSSL SHA1, we could use a Microsoft
>> hash
>> function.
>>
>> Thus we do not depend on #ifdef ENABLE_OPENSSL for this one purpose.
>>
>
> Ok, this is
Hi Viktor/all,
It seems that in the following commit to the secure-messaging branch - "pkcs11:
rewrite
pkcs15_create_tokens() -- use static sub-funcs" - the requirement for a private
key to have a link
to a PIN ID got a bit stricter. In previous versions, it seems that if an
object wasn't add
Le 05/12/2011 14:37, Viktor Tarasov a écrit :
> Hello Jean-Pierre,
>
> Le 05/12/2011 11:27, Jean-Pierre Fortune a écrit :
>> Could this behaviour be related to the fact that the private key is
>> not allowed to sign?
>> Where could I patch the code to force the use of this key?
>
> afais, you a usi
