Replacing HTML5's <keygen> - Looks like a project

HTML5's <keygen> may not even reach last call before it will be a
subject for replacement.

http://www.ietf.org/mail-archive/web/pkix/current/msg29641.html

This does not come as a surprise to me since <keygen> was kept on
historical merits rather by being preceded by market research or
requirement specifications.

However, the real battle will be between Microsoft's "MiniDriver" and
"Unified Tokens" of the kind I'm advocating.  IMHO adapting the OS
or browser platform is *much cheaper* and *faster* than qualifying
tons of dubious third-party drivers!  

That's BTW exactly how Apple would do it, so it simply has to be right :-) :-)

A peek in http://www.opensc-project.org/pipermail/opensc-devel verifies
my claim that *abstracting token APIs is a never-ending story*.

Regards,
Anders

Received on Saturday, 13 August 2011 16:18:30 UTC