4 ms·
It kind of saddens me that the W3C is willing to focus on things like DRM, but not a public-key implementation for browser vendors. Yeesh.
by 1qaz2wsx3edc 13y ago
It kind of saddens me that the W3C is willing to focus on things like DRM, but not a public-key implementation for browser vendors. Yeesh.
- 0x0 13y agoWell, there is always the html5 <keygen> tag? http://www.w3.org/TR/html-markup/keygen.html http://www.w3.org/TR/html-markup/keygen.html https://developer.mozilla.org/en-US/docs/HTML/Element/keygen https://developer.mozilla.org/en-US/docs/HTML/Element/keygen
- nly 13y agoWhat!? No demoscene music in my <keygen> ?
- drdaeman 13y agoActually, there's a W3C WG that works (worked?) on a protocol called WebID, that uses public keys to authenticate users, and servers are not identity providers but just serving profile information. http://www.w3.org/2005/Incubator/webid/spec/#authentication-sequence http://www.w3.org/2005/Incubator/webid/spec/#authentication-...
- Flimm 13y agoSSL includes a feature called client-side certificates: http://pilif.github.io/2008/05/why-is-nobody-using-ssl-client-certificates/ http://pilif.github.io/2008/05/why-is-nobody-using-ssl-clien...