3 ms·
You know, this has always bothered me to a certain extent. We have self-signed certificates, and we have CA certificates, but couldn't we have an in-between opt
by zeta0134 8y ago
You know, this has always bothered me to a certain extent. We have self-signed certificates, and we have CA certificates, but couldn't we have an in-between option? Say, a self-signed certificate which suggests to the browser that it could be installed locally.
The browser could still displays a warning once, "Warning! We can't determine whether we should trust this site. It claims to be [Such and such local service.] Would you like to trust this site? [Yes, temporarily], [Yes, permanantly (installs local certificate)], [No, get me out of here!]
Firefox already does something like this, but its wording is kind of vague, and the strong assumption from browser vendors seems to be CA or bust. The truth is, encryption is useful in some very common cases where a CA or a domain name is simply not feasible, and we need workarounds for those use cases that don't feel like a dirty hack for techies only.