109 karma · joined June 26, 2012
We have been doing this for years in .ee, and the user experience has been mediocre. And this is something we can not fix (browser vendors can). The future promises to be FIDO, but then again, this is a different model, that mostly addresses authentication ONLY.
I just started a weekend project to bring the hardware token based authentication to a state that it could be called "standardized", for the huge EU market, where very many citizens in different countries have a vetted PKI identity on the eID smart card.
Might be of interest. https://github.com/martinpaljak/x509-webauth/wiki/WebAuth The core of it is just a profile of OpenID Connect ID Token, with fresh browser extensions with native messaging support to facilitate actual communication to hardware tokens.
Standards that are necessary for basic interoperability should be all free (at least in the software space, maybe that's why I see standards that get "promoted" from IETF RFC-s and other less bureaucratic sources to ISO as regressions). And the ones that are usually used in regulatory processes, can be paid for, as those who insist on or desire conformance usually have monetary incentives involved.
Now, charging for "standards" that contribute to "public safety and security" (what MANY C programs are, for sure) is something that does not fit into either category.
But true, the MISRA prices are reasonable (if the content is indeed worth any money for purposes other than compliance).
I would not bet that I've committed a crime by searching the web for information (what the web is for), I think that where I live (northern part of EU) this is an OK thing to do.
* because the user experience really requires you to have the "nascar effect" of several well-known icons. OpenID could scale horizontally technically but in fact it doesn't work that way. Except for a few providers (like Google) it is not "peer to peer" (many to many) but more like "business to customers" (one to many) relation
* because the "like"-generation beloved blue button talks something else (and is "way more important" than some technical nice thing)
* because it requires putting too many eggs in one basket (one ID to rule them all. And even "the few big ones" are these days hacked without problems)
* because your database of users is your asset (at least in the US). In EU it is more often a liability. * As this is an asset, nobody wants to pay anything for a secure identity as a TTP service.
* because it forbids "sensible" use on mobile devices (I have a phone and a PC, I would like to link my phone(s) to my services through numbers rather than on-phone cumbersome username or openid hack)
* pairing with a QR code works well for me. It even allows to establish a more meaningful key for further communication (I check the "green bar" of the browser than the underlying, semi-anonymous, DNS-depending OpenID)
* because OpenID does not really work for anything than medium-security identification transport. I hope my bank will never use an OpenID to authenticate anything.
* just try a new service with a throwaway account. or a throwaway password. Maybe one day people build services, which do not require pairing to "something" at all. Or Just use "click-the-link-in-e-mail-or-copy-token" approach.