On 2011-10-14 17:12, NdK wrote: > On 14/10/2011 12:34, Tomas Gustavsson wrote: > >> There was still mentioning about smart card middleware in the article. I >> didn't quite get it, but anything that still requires installation of >> different middle-wares for different cards does not bring us much closer >> to a "token enabled" world imho.
> Well, as long as you use 24727-compliant cards you can have only one > middleware installed. > > Surely someone will be able to misinterpret specs so that incompatible > cards will appear... but that's another story. If I understood it right, the idea behind 24727 is to abstract things to a high-level so you don't have to deal with them. So far so good. However, the net effect of this is that the application, driver etc. must interrogate the framework to see if the underlying hardware can do this and that. If you ever have worked with automated testing using JUnit or similar you would see the problem: A project that never finishes. Sounds a bit like OpenSC :-) BTW, abstracting end-to-end security has proved to be hard if not downright impossible. The absolute "antithesis" of 24727: http://webpki.org/papers/keygen2/sks-keygen2-exec-level-presentation.pdf Open Security Hardware is the magic ingredient that (at least on paper) could rock this somewhat stagnant industry segment. Anders > The (not-so-)"bad" thing is that it won't map well on pkcs-11, so many > programs will need a different middleware... I hope that finally Firefox > will work "as expected" :) > > BYtE, > Diego. > > _______________________________________________ > opensc-devel mailing list > opensc-devel@lists.opensc-project.org > http://www.opensc-project.org/mailman/listinfo/opensc-devel > _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
