Hi, Afais, currently there are five cards that have private key implemented as BSO - Base Security Object (or SDO - Security Data Object).
These cards need in the 'key-domain' template of their profile some 'dummy' EF private-key entry with the file-id = FFFF. In reality, for these cards, with the core procedures the 'private-key' template is instantiated with invalid path (the last two bytes are FF FF), and then this path is overwritten by correct value (df->path) in the card-specific part . As consequence, path for these objects are not really defined by profile. I propose to change it: introduce new type BSO, and in the profile.c treat it differently from normal EF. Advantages are: - path for BSO is set with the general procedure; - path for BSO is really defined by profile; - less of the odious workarounds. I've tested this approach with oberthur (not-BSO) and CardOS (BSO). Any objections? Kind wishes, Viktor. -- Viktor Tarasov <[email protected]> _______________________________________________ opensc-devel mailing list [email protected] http://www.opensc-project.org/mailman/listinfo/opensc-devel
