Hi Andreas,
Andreas Jellinghaus wrote:
> Am Freitag 19 März 2010 15:10:29 schrieb Viktor TARASOV:
>
>> I would like to start to submit the support for the cards IAS/ECC as it
>> defined in 'Gixel' specification [1] .
>> File system of this card is based on PKCS#15.
>>
>
> good idea! go for
Hello,
Martin Paljak wrote:
> On Mar 19, 2010, at 16:10 , Viktor TARASOV wrote:
>
>> Hi,
>>
>> I would like to start to submit the support for the cards IAS/ECC as it
>> defined in 'Gixel' specification [1] .
>> File system of this card is based on PKCS#15.
>>
> 1. Is there a public and w
On Mar 22, 2010, at 11:40 , Viktor TARASOV wrote:
> Actually I don't know how to get low card volume .
> These cards are produced by Sagem, Gemalto and Oberthur .
> I imagine there could be found the contacts.
smartcardfocus.com sells Cosmo v7 cards with PIV applet pre-loaded. I believe
it might
Hello Smartcard Focus Sales,
On Mar 22, 2010, at 11:40 , Viktor TARASOV wrote:
>> 1. Is there a public and working source for low volume purchases of a card
>> with IAS/ECC applet pre-loaded?
>>
>
> Actually I don't know how to get low card volume .
> These cards are produced by Sagem, Gemalto
I added a new option to the card driver definitions:
ignore_version_check. It would be possible to add it to the official
version? I am searching for alternatives for solving the problem not
for me but for all the spanish users of opensc.
--- src/libopensc/ctx.c.old 2009-07-23 10:57:46.0
hi OpenSC team,
we have started to use a PKCS#11 URI for accessing objects in
the tokens in OpenSolaris and we also wrote an I-D draft to document the
scheme. Given that your project also use the PKCS#11 spec, more
precisely I can see that you use your own way of accessing PKCS
Dear friends,
Reading the wiki, I understand that the Mac OS X SCA experimental build
should include a recent version of OpenSC. Does it include OpenSC
0.11.13, which is need for good support of the Feitian PKI?
What is needed to make an experimental build? I have a Mac OS 10.5
somewhere in the o
Hello,
If your browser or SVN client is configured to warn you if the certificate of
the server has changed, don't be alarmed if you see tomorrow a new certificate
with the following fingerprints:
SHA1: 17 BE 7F 71 EB 84 2D 91 B1 A4 36 D5 63 44 08 F7 4D 5F B5 1A
MD5: AF B0 2C BC 41 82 C0 DD A9
