> PKCS#15 card producers resolve this problem by > creating parallel CSP file system, invisible for PKCS#15, > or by creating 'DATA' objects with the common 'application' attribute, > for ex. "BaseCSP". > > I guess that this second approach is more appropriate for the OpenSC > minidriver. > > The capability of the card to support 'write' minidriver mode will be > declared in 'card_atr' section of opensc.conf. > It presumes that card supports the pkcd15-init. > For such card all pkcs15-init operations (executed by tools, pkcs#11 > or minidriver) will try to update the BaseCSP 'DATA' objects. > > What do you think about?
Dear Viktor,
IMHO this is a very interesting way to go.
When using OpenSC under Mac OS X or GNU/Linux, it also assumes that
OpenSC should write these invisible information to preserve
compatibility under all systems.
I presume this would make OpenSC a universal platform.
Kind regards,
--
Jean-Michel Pouré - Gooze - http://www.gooze.eu
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
