Hello Viktor, > Andre Zepezauer wrote: > >>> Besides the sigh_with_decipher hack there is another problem which > >>> arises when on card pkcs15 structure states only one operation per key. > >>> > >>> > >> It's the subject of the next enhancement. > >> I suggest something like > >> http://www.opensc-project.org/opensc/browser/branches/vtarasov/opensc-sm.trunk/src/libopensc/pkcs15-prkey.c#L38 > >> > > > > This is the definition form PKCS15 v1.1 > > > > CommonKeyAttributes ::= SEQUENCE { > > iD Identifier, > > usage KeyUsageFlags, > > native BOOLEAN DEFAULT TRUE, > > accessFlags KeyAccessFlags OPTIONAL, > > keyReference Reference OPTIONAL, > > startDate GeneralizedTime OPTIONAL, > > endDate [0] GeneralizedTime OPTIONAL, > > ... -- For future extensions > > } > > > > Where did you find the following redefinition? > > > In the card application profiles recommended by French government for > the IAS/ECC cards. [1] > > > > http://www.opensc-project.org/opensc/browser/branches/vtarasov/opensc-sm.trunk/src/libopensc/pkcs15-prkey.c#L56 > > > > Look also > http://www.opensc-project.org/opensc/browser/branches/vtarasov/opensc-sm.trunk/src/libopensc/pkcs15.h#L312 > > The main idea is, > for the algorithms supported by key, keep in it's 'prkey_info' the > references to the algorithms supported by card and defined in 'tokenInfo'.
Time to pick up 7816-15, because [1] is based on it ;) > [1] > http://www.references.modernisation.gouv.fr/sites/default/files/MDWIAS_Profils%20de%20%20personnalisation%20des%20cartes%20IAS%20%20V2_7.pdf _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
