I looked at the two logs you sent, and I don't see where the private
key is generated on the card, or where the Globus private key was written
to the card. I don't have any of these cards, so I may have missed
something. I would have expected the log to have some entries for
entersafe_gen_key, or
Hi Viktor,
ISO 7816-15:2004 defines read(0), update(1), execute(2) and delete(3).
Andreas
Viktor TARASOV schrieb:
> Hi,
>
> The 'accessMode' bit string, encoded by the native Oberthur middleware
> for the IAS/ECC cards,
> can be up to 10 bits length.
>
> In PKCS#15 (v1.1) for the 'accessMode' o
Hi,
The 'accessMode' bit string, encoded by the native Oberthur middleware
for the IAS/ECC cards,
can be up to 10 bits length.
In PKCS#15 (v1.1) for the 'accessMode' only three bits defined: 'read',
'update', 'execute'.
In ECC specification (CEN/TS 15480-2:2007) one more: 'delete'.
Have you an
On Fri, 21 May 2010 02:41:21 +0800, Andreas Jellinghaus
wrote:
> It would be great if the entersafe driver could be improved
> to the point, where src/test/regression/ test suite works
> with the cards. The test suite provides a very good way for
> us to test many different card features, and m
On Fri, 07 May 2010 18:36:39 +0800, Jan Just Keijser
wrote:
More information for the Feitian folks: I also tried the driver bundle
from the ftsafe website but it only supports the SCR200 card reader, not
the 301 ; what was/am I doing wrong there?
Thank you for testing Feitian products, AFAIK SC
Viktor TARASOV wrote:
> Jan Just Keijser wrote:
>
>> Jean-Michel Pouré - GOOZE wrote:
>>
>>
>>> On Thu, 2010-05-20 at 12:35 +0200, Jan Just Keijser wrote:
>>>
>>>
>>>
At this point I downloaded and built opensc-0.11.13
>>> As explai
Douglas E. Engert wrote:
> After looking at your
> http://www.nikhef.nl/~janjust/feitian/opensc-debug.log-20100520
> and reading these mails again, this does not look like a reader or pcsc
> problem. You were not able to write your Globus key to the card,
> and were not able to generate a key on
