Am Freitag 05 März 2010 18:34:18 schrieb Greg Mefford:
Anyone using this card successfully in any capacity that could help me
get started? Once I understand how this thing works, I'm interested in
making it work with OpenSC, but if it currently only works on Windows,
that's fine for now.
hmm,
On 5 Mar 2010, at 17:34, Greg Mefford wrote:
It seems like the card software includes some
Windows tools (which is fine with me if that's what it takes to get
started) and a bunch of technical documentation, but not much
practical help in how to actually use the thing.
Right. As far as I
Hi,
in the OpenSC pkcs#11 module the CKA_ID of the CA certificates is
reported as '0'.
There is Olaf's comment: Not sure why CA certs should be reported with
an ID of 00 --okir 20030413
What for it was done? Is it still valid?
Kind wishes,
Viktor.
--
Viktor Tarasov
Thanks for your thoughts. I have since spent some time debugging with
Windows as suggested and made some headway.
I believe I ran into some of the same non-standard problems you
mentioned about the file structure the Initialization Tool installs. I
go to do a simple thing like dump all the files
On Mar 9, 2010, at 03:34 , Greg Mefford wrote:
Thanks for your thoughts. I have since spent some time debugging with
Windows as suggested and made some headway.
I believe I ran into some of the same non-standard problems you
mentioned about the file structure the Initialization Tool installs.
On Mar 3, 2010, at 12:08 , Andreas Jellinghaus wrote:
Am Mittwoch 03 März 2010 08:46:27 schrieb Martin Paljak:
Tokend still requires access to libopensc headers, having it in a standard
place (/Library/OpenSC/include) would ease the building of it, as it would
not require any changes in xcode
I propose to change the sc_pkcs15_verify_pin() prototype from
int sc_pkcs15_verify_pin(struct sc_pkcs15_card *, struct
sc_pkcs15_pin_info *, const u8 *, size_t);
to
int sc_pkcs15_verify_pin(struct sc_pkcs15_card *, struct
sc_pkcs15_object *, const u8 *, size_t);
The reason is that
