Hello, On Aug 3, 2011, at 6:22 PM, NdK wrote: >> On Windows, you could also use the Windows CAPI via the SunMSCAPI, >> and OpenSC on Windows can still be used via the OpenSC mindriver. > Still proprietary solutions. > And what about smartphones? "Standard" Java is more likely to be adapted > than proprietary interfaces.
I don't believe that current smartphone platform vendors will embrace PKCS#11 as we know it on the desktop. At least I hope they will not. It would IMHO be a stupid choice. Java is a platform itself, so JCE/JCA could be the key, if anything. It might not be perfect or even most suitable. I agree with Anders that enrollment with mobile devices (with built-in security tokens) should eventually become as important as using keys. Take Android - it does not make use of "standard" Java API-s (Swing), yet it is very successful. Being able to "run the code" does not mean "having sensible support for a platform with minimal or no code changes". When developing a "portable" application (in Java..) I would not bet much on PKCS#11 or similar. For optimal results assume that PKCS#11 is not available. My personal suggestion is to omit the "proprietary" excuse. Whenever running *anything* on Windows (or OS X), you are using a proprietary platform. Either refuse to run on it or try to live with it and make the most out of it by using the services provided by the platform is possible and providing users with as good experience as possible. Best, m. -- @MartinPaljak.net +3725156495
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
