Definitely useful, I agree!
I currently use a mix of engine_pkcs and PKCS#11 calls in order to do my
stuff, which is akward.
On 12/05/2011 06: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
Hi all,
I'm successfully using dozens of smart cards at the same time with an
appliance that I develop for my company.
The experience I can bring to the table is that many PKCS#11 drivers go
nuts with just a few readers / smart cards, so the limit you will
finally experience mostly lies in th
Andre Zepezauer wrote:
> On Thu, 2010-09-23 at 15:50 +0200, Andre Zepezauer wrote:
>
>> On Thu, 2010-09-23 at 14:19 +0200, Umberto Rustichelli aka Ubi wrote:
>>
>>> Dear all, I have been digging a bit into the OpenSC and OpenSSL code
>>> because I have
Dear all, I have been digging a bit into the OpenSC and OpenSSL code
because I have a doubt.
Using keys on smart cards via the OpenSC engine, I am almost sure that
by producing a PKCS7 the signature is of type "sha1WithRSAEncryption"
(at least without any special options), that implies using
I see the function parse_slot_id_string in engine_pkcs11.c ends with:
/* ... or "label_" */
if (strncmp(slot_id + i, "label_", 6) == 0)
*slot = n;
return (*label = strdup(slot_id + i + 6)) != NULL;
fprintf(stderr, "could not parse string!\n");
