On Friday april 22 2011 18:46:29, Viktor TARASOV wrote:
> Le 22/04/2011 16:14, BLANC Gilles a écrit :
> > On thursday april 21 2011 19:39:32, Viktor TARASOV wrote :
> >> Hello,

Hi Viktor, sorry for my late answer, I was very busy this week...  :/

> >> Le 21/04/2011 14:51, BLANC Gilles a écrit :
> >> Try to repeat your tests with the latest trunk .
> >
> > Done, same problem.  :/
> 
> What tools are you using ?

Idrix cryptoki. Nice tool to test pkcs11 interface.

> Start with:
> #opensc-tool --name --serial
> 11 11 11 11 11 11 11 1F ........
> IAS/ECC v1.0.1 Oberthur

This is ok

> #pkcs15-tool --list-applications
> Application 'OT AWP C_V0.2':
>      AID: E828BD080FF2504F5420415750
>      DDO: 4F0DE828BD080FF2504F5420415750

I have the same.

> #pkcs15-tool --list-pins
> ...

This works great.

> If there are problems at this step, send me the debug logs (level 8, in
>  opensc.conf).
> 
> >> The profile of the oberthur's 'generic PKI' application was obsolete .
> >
> > I see that you have modified the file
> > "src/pkcs15init/iasecc_generic_oberthur.profile". But it does not seem to
> > have influenced my case.
> >
> > (how does that file work ? Do I need to change a configuration file
> > somewhere ?)
> 
> No, normally you do not need changes in configuration.
> 
> Profiles are used only by pkcs15init bind (the on-card data are going to be
>  changed) . Pkcs15 bind or opensc tools do not use it (the on-card data 
>  will not be changed) .

ok

> How it works:
> - card (and its driver) is recognized by ATR;
> - pkcs15init binding starts by load of the general pkcs15.profile;
> - then loaded the profile with the same name as a card's driver (the
>  profile setting with the same name will overwrite the ones from the
>  generic profile); - for the IASECC cards there is an additional step:
>  after the 'DIR' pkcs15 file has been read and the list of the on-card
>  applications has be defined, the final profile part is loaded
>  (iasecc_generic_oberthur). This final part is identified by AID of
>  application .

ok, thank you !

> >> Does your card has pre-allocated key-slots ?
> >> Creating of a new key-slots is not yet implemented (ported from the
> >> IAS/ECC dedicated branch).
> 
> Well, this weekend I will look how far we can go with the Oberthur's
>  IAS/ECC card and with actual trunk . (I do not much played with the last
>  Oberthur's card.)

I have seen that you have modified some things. Sadly, I still encounter the 
same problem by now...

> > I don't know, actually. I'm going to ask the right person...
> 
> Can you ask the 'right person' if your card contains the biometric data,
>  supports EC algos ... ? It would be quite interesting.

This is possible to include it, but it is not the case for my card (and it 
will not be so: these options are quite expensive and special, to my 
understanding).


Thanks for your help,
-- 
Gilles Blanc - gbl...@linagora.com
Ingénieur expert informatique embarquée
Représentant du personnel - Secrétaire du CE
Groupe LINAGORA - http://www.linagora.com
Tél.: +33(0)1 46 96 63 39 - Fax : +33(0)1 46 96 63 64
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to