2 ms·
Well, my point was that no direct connection is possible - and that used to be a completely trivial thing to do before HTTPS Everywhere. I argue, the amount of
by xg15 8y ago
Well, my point was that no direct connection is possible - and that used to be a completely trivial thing to do before HTTPS Everywhere. I argue, the amount of times companies try and fail to do risky acrobatics with custom certs shows that there is still demand for that use-case.
> directly insert a leaf certificate (not a root cert) into the platform key store
This would amount to pre-installing exceptions for self-signed certificates. I may be wrong, but I think this is something most major browsers manage themselves, not the platform - and I'm not sure there is even an API for it. Even if there is, at least Chrome seems to regularly remove the exceptions.
> don’t try to hide that you’re running a local host server.
I'm not aware of anyone trying to do this. From my understanding the "localhost.company.tld" DNS entries are to get around restrictions set by the browsers (which were slightly loosened since), not to fool end-users.
> use an app (this is an option)
If you can get the user to install an app, you don't need the browser at all. I think the use-case is connecting to the device without installing anything at all. This used to be an easy thing to do - just run an HTTP server on the device - but seems to have no direct equivalent with HTTPS.
I admit, I think the discussion threw two different use-cases together: Communicating between non-localhost HTTPS <-> localhost and communicating between non-localhost HTTPS <-> local device.
The former is possible, even though you have to jump through a few risky hooks to do it and can quickly open up gaping security vulnerabilities if you do it wrong.
The latter doesn't seem to be possible without a cloud service or local helper app as an intermediary.