Re: [opensc-devel] Problems developing with Starcos 2.3

Fernando Sanchez Chaparro wrote: > Hi Andreas, Thank you very much for your answer. > > 2010/2/4 Andreas Jellinghaus > > > Hi Fernando, > > your problem is this: >starcos_ops.delete_file = NULL; > > the starcos driver does not implement delete f

Re: [opensc-devel] Problems developing with Starcos 2.3

Hi Andreas, Thank you very much for your answer. 2010/2/4 Andreas Jellinghaus > Hi Fernando, > > your problem is this: >starcos_ops.delete_file = NULL; > > the starcos driver does not implement delete file. > > I'm not sure of the details, maybe it is a limitation of the card > (i.e. sta

Re: [opensc-devel] Problems developing with Starcos 2.3

Hi Fernando, your problem is this: starcos_ops.delete_file = NULL; the starcos driver does not implement delete file. I'm not sure of the details, maybe it is a limitation of the card (i.e. starcos does not offer any way to delete files). not 100% sure. it could also be that the driver a

Re: [opensc-devel] Problems developing with Starcos 2.3

Andreas Jellinghaus wrote: hmm. is that new? the resellers I know did sell etokens fine, even if I wanted to buy only one or two and no software. It could just be my vendor. We are encouraged to use CDW. ___ opensc-devel mailing list opensc-deve

Re: [opensc-devel] Problems developing with Starcos 2.3

Am Mittwoch 03 Februar 2010 19:24:16 schrieb Jim Rees: > Andreas Jellinghaus wrote: > > what about the cyberflex tokens from axalto? I think they are still sold. > > They were discontinued some time ago, but some vendors still have a few in > stock. Too bad, they and Cryptoflex were my favorit

Re: [opensc-devel] Problems developing with Starcos 2.3

On Feb 3, 2010, at 21:31 , Andreas Jellinghaus wrote: >> Can't remember how it was with the 1.0/1.1 card, which I still have >> (but it got locked up a long time ago). V2.0 supports x509 >> certificates. > > ah, nice. does opensc support the new cards too? No. http://www.opensc-project.org/opens

Re: [opensc-devel] Problems developing with Starcos 2.3

Am Mittwoch 03 Februar 2010 20:17:09 schrieb Martin Paljak: > I really would like to have something that would withstand my usage > (be waterproof and mudproof, withstand being in a keyring with keys > etc) but at the same time be standards compliant (CCID) and have a > reasonably good chip inside.

Re: [opensc-devel] Problems developing with Starcos 2.3

2010/2/3 Andreas Jellinghaus : > Am Mittwoch 03 Februar 2010 17:27:17 schrieb Martin Paljak: >> I also have SIM size readers but that's not the same as a sturdy >>  keychainable token. Probably the durability is the major piece in the >>  price tag. > > my experience with some tokens is not so good

Re: [opensc-devel] Problems developing with Starcos 2.3

Andreas Jellinghaus wrote: what about the cyberflex tokens from axalto? I think they are still sold. They were discontinued some time ago, but some vendors still have a few in stock. Too bad, they and Cryptoflex were my favorite cards. Aladdin USB tokens are ok I guess. One problem with Alad

Re: [opensc-devel] Problems developing with Starcos 2.3

Am Mittwoch 03 Februar 2010 17:27:17 schrieb Martin Paljak: > I also have SIM size readers but that's not the same as a sturdy > keychainable token. Probably the durability is the major piece in the > price tag. my experience with some tokens is not so good. if you do bad things every token bre

Re: [opensc-devel] Problems developing with Starcos 2.3

On Feb 3, 2010, at 17:52 , Andreas Jellinghaus wrote: > Am Mittwoch 03 Februar 2010 16:41:12 schrieb Martin Paljak: >> I only have epass3k and e-gate tokens. Any good tokens that speak CCID/ICCD >> and cost less than 50€ and have a JavaCard or some other decent native OS >> inside? Aladdin and Athe

Re: [opensc-devel] Problems developing with Starcos 2.3

Andreas Jellinghaus wrote: > Am Mittwoch 03 Februar 2010 16:34:41 schrieb Viktor TARASOV: > >> Andreas Jellinghaus wrote: >> >>> Am Mittwoch 03 Februar 2010 14:50:15 schrieb Viktor TARASOV: >>> In cryptoshop.com there is 'developer version of the StarCOS SPK 2.3'. Is it sim

Re: [opensc-devel] Problems developing with Starcos 2.3

Am Mittwoch 03 Februar 2010 16:41:12 schrieb Martin Paljak: > I only have epass3k and e-gate tokens. Any good tokens that speak CCID/ICCD > and cost less than 50€ and have a JavaCard or some other decent native OS > inside? Aladdin and Athena seem nice but the price tag is not OK for a > toy. w

Re: [opensc-devel] Problems developing with Starcos 2.3

Am Mittwoch 03 Februar 2010 16:34:41 schrieb Viktor TARASOV: > Andreas Jellinghaus wrote: > > Am Mittwoch 03 Februar 2010 14:50:15 schrieb Viktor TARASOV: > >> In cryptoshop.com there is 'developer version of the StarCOS SPK 2.3'. > >> Is it similar to the card that your are using? Can this card be

Re: [opensc-devel] Problems developing with Starcos 2.3

On Feb 3, 2010, at 17:34 , Viktor TARASOV wrote: > Should I use OpenCT? install ifdHandler from SafeNet? If you have an alternative driver than OpenCT, you can use it (and thus use it on non-linux platforms as well) "From where to get USB token drivers" should be written out clearly in the wiki

Re: [opensc-devel] Problems developing with Starcos 2.3

Andreas Jellinghaus wrote: > Am Mittwoch 03 Februar 2010 14:50:15 schrieb Viktor TARASOV: > >> In cryptoshop.com there is 'developer version of the StarCOS SPK 2.3'. >> Is it similar to the card that your are using? Can this card be >> initialized and used with OpenSC ? >> > > should be fin

Re: [opensc-devel] Problems developing with Starcos 2.3

Am Mittwoch 03 Februar 2010 14:50:15 schrieb Viktor TARASOV: > In cryptoshop.com there is 'developer version of the StarCOS SPK 2.3'. > Is it similar to the card that your are using? Can this card be > initialized and used with OpenSC ? should be fine. I only have a "rainbow ikey 3000", but it con

Re: [opensc-devel] Problems developing with Starcos 2.3

Fernando Sanchez Chaparro wrote: > Thank you for your answer Viktor. > > 2010/2/2 Viktor TARASOV > > > Fernando Sanchez Chaparro wrote: > > Finally, I found how to solve my problem thank to your answers. I > > really appreciate the help I have recei

Re: [opensc-devel] Problems developing with Starcos 2.3

Thank you for your answer Viktor. 2010/2/2 Viktor TARASOV > Fernando Sanchez Chaparro wrote: > > Finally, I found how to solve my problem thank to your answers. I > > really appreciate the help I have received from this list. > > > > The problem was that I had initialized the smart card with onl

Re: [opensc-devel] Problems developing with Starcos 2.3

Fernando Sanchez Chaparro wrote: > Finally, I found how to solve my problem thank to your answers. I > really appreciate the help I have received from this list. > > The problem was that I had initialized the smart card with only the SO > Pin, and therefore the opensc-pkcs11.dll didn't find any

Re: [opensc-devel] Problems developing with Starcos 2.3

Finally, I found how to solve my problem thank to your answers. I really appreciate the help I have received from this list. The problem was that I had initialized the smart card with only the SO Pin, and therefore the opensc-pkcs11.dll didn't find any slot. Using the onepin profile (pkcs15-init -

Re: [opensc-devel] Problems developing with Starcos 2.3

are you trying to get new blank card initialized with opensc to work, or are you trying to get cards with that vendors software to work with opensc? if that vendor did not implement PKCS#15 on the cards, the resulting card might not be compatible with opensc. opensc is supposed to be compatible w

Re: [opensc-devel] Problems developing with Starcos 2.3

Hi Fernando, it is best to check the command line utilities like "pkcs11-tool --test --login" to see if these is a general problem. if there is not, you could use pkcs#11 spy (pkcs11-spy.dll) and hook it between your application and opensc-pkcs11.dll. it will generate a log file of all your functi

Re: [opensc-devel] Problems developing with Starcos 2.3

>I cannot offer more information about my problem since my program doesn't have >runtime errors or compiled errors, can I? You can get more information try to configure "opensc.conf" put debug = 9 instead of debug = 0. François. ___ opensc-devel