4 ms·
only as screwed as we allow ourselves to be. authority is given by tacit consent of those subjected to it. there are free and/or open CAs and the moment cert re
by rolph 8y ago
only as screwed as we allow ourselves to be.
authority is given by tacit consent of those subjected to it.
there are free and/or open CAs and the moment cert revocation becomes a big issue is when the current CAs lose authority and are succeded by grass roots CAs.
this will take some browser twiddling and brand conversion, as the current framework for HTTPS certification extends to whitelist and blacklists of ^unvetted^ certificates, in a manner homologous to emailserver blacklists.
in other words, you can roll your own but the current infrastructure can blacklist it. its a big job but not yet impossible.
or we could forget all this business about encrypting the protocol [HTTP>HTTPS] and simply encrypt the page moving via the protocol, when there is a concern for privacy.
that being said, the whole point of publishing to the web, is so that everyone can see it.
if you want to publish to an exclusive group, then use a different protocol, that is not clear in public, and not reliant on third party mechanisms.