Hello, I have A-trust card.
Opensc support it throw build in emulation, in code card detected as "atrust-
acos", but opensc.conf from last Smart card bundle(scb-0.8.exe) have const
"atrust-acosi". Is it typing error?
___
opensc-devel mailing list
op
Hi,
I like to know meaning of following operation flag
SC_AC_OP_REHABILITATE,SC_AC_OP_INVALIDATE. Can any one
please explain me what these flags mean.
Regards,
Kamal.
Got a little couch potato?
Check ou
Corcoran David wrote:
> Hi,
>
> Is this an issue from the CSP -> OpenSC PKCS#11 module ?
Yes, looks like the CSP calls C_Finalize after the the card is removed.
then when a card is inserted, it does not not call C_Initialize
but calls C_OpenSession. I suspect the problem is in that handles
the
Andreas Jellinghaus dungeon.inka.de> writes:
>
> you can either:
> a) store the key for decryption only, see the --key-usage parameter to
> pkcs15-init.
> b) store the key as split key: opensc will store the keys twice, once for
> signing and once for decryption, and magically choose the right
On Monday 16 July 2007 10:28:58 Dmitry wrote:
> Opensc support it throw build in emulation, in code card detected as
> "atrust- acos", but opensc.conf from last Smart card bundle(scb-0.8.exe)
> have const "atrust-acosi". Is it typing error?
yes, fixed in commit 3008. scb 0.9 with this fix most lik
