Well said DW. Very interesting to say the least! ;,) RAC On Mon, Mar 21, 2022, 11:11 AM element crew <[email protected]> wrote:
> > The HTML element exists to facilitate generation of key material, and > submission of the public key as part of an HTML form. This mechanism is > designed for use with Web-based certificate management systems. It is > expected that the element will be used in an HTML form along with other > information needed to construct a certificate request, and that the result > of the process will be a signed certificate > > https://elementtutorials.com/ref/keygen.html > <https://the%20html%20element%20exists%20to%20facilitate%20generation%20of%20key%20material%2C%20and%20submission%20of%20the%20public%20key%20as%20part%20of%20an%20html%20form.%20this%20mechanism%20is%20designed%20for%20use%20with%20web-based%20certificate%20management%20systems.%20it%20is%20expected%20that%20the%20element%20will%20be%20used%20in%20an%20html%20form%20along%20with%20other%20information%20needed%20to%20construct%20a%20certificate%20request%2C%20and%20that%20the%20result%20of%20the%20process%20will%20be%20a%20signed%20certificate%20%20https//elementtutorials.com/ref/keygen.html> > On Thursday, 20 April 2017 at 22:50:35 UTC+5:30 Dirk-Willem van Gulik > wrote: > >> On 20 Apr 2017, at 18:49, Chris Palmer <[email protected]> wrote: >> > >> > On Thu, Apr 20, 2017 at 9:38 AM, Dirk-Willem van Gulik < >> [email protected]> wrote: >> > >> > But none of this complexity seems to warrant killing of a very key (pun >> intended) element that secures the distributed open web; that makes it >> possible for entities to forge strong peer to peer trust relations; without >> a central broker, `login with xxx' button or account 'master' or other >> dominant party being `in' on the trust setup. >> > >> > You might be interested in >> https://fidoalliance.org/specifications/overview/. >> >> Aye - well aquatinted with that - and I totally agree that this is an >> important /additional/ arrow in our quiver - one I recommend & use lovingly >> in specific settings. And its approach to things such as certification and >> trademark licensing are very valuable and commendable for a certain class >> of federated, distributed login systems. >> >> However I think it is key to *ALSO* retain the open web its ability to >> foster distributed, federated trust relations between parties who have >> never met; who are not part of the same club, who are `barely legal' or are >> in strange places, remote places. >> >> When I started working on apache and HTTP - it was, as a technology, not >> even fully 'legal' to touch in most countries around the world. Heck - I >> had to argue with the powers that be as to why 'auth' was even to be >> `allowed'* in conjunction with HTTP. >> >> So I really value strong crypto that is fully open world. That requires >> no membership card, no special hardware, no special coordination, no >> certification, no trademark, no natural need to have a third party enter >> the deal as a relying party; or look odd if that is a specific one/setup. >> >> Nothing but the 'spec' and a bit of honest work on the server. And is >> supported in any and all browsers. And nothing but a browser; your server - >> and *all* that is needed to share trust in this distributed/federated setup >> is the decision by the party that trust to start trusting. And all that it >> needs for that is a public key. No shared secrets, no 'deals', no licenses, >> nothing that is not already a 100% under control of the party that wants to >> trust. >> >> Even though (or especially though) I full well realise that most people >> with money and standing prefer to login through facebook or google - or >> will have the latest FIDO compliant device. >> >> I want that next generation of hackers to have that freedom. The freedom >> I personally needed to help get the web to were it is now. >> >> The need to collaborate or trust - without needing permission or >> assistance. >> >> Dw. >> >> *: (as it was not an ITU standard, not X.25 based, no X.500 directory >> base for login). >> >> >> -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6933bf17-846a-49e4-9421-952f625d57d0n%40chromium.org > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6933bf17-846a-49e4-9421-952f625d57d0n%40chromium.org?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACejsYmSq8Yq4pbrc8QF%3DcDLVfJ7Rp3DAcYF4zTLbej7fMMcSg%40mail.gmail.com.
