3 ms·
Uhh there are plenty of ways. Those pretty peering graphics new devices have are used to establish trust (sharing per device certificates or encryption keys).
by olliej 8y ago
Uhh there are plenty of ways. Those pretty peering graphics new devices have are used to establish trust (sharing per device certificates or encryption keys).
You can also establish over Bluetooth or audio - you just need a small side channel to create the initial trust.
- xg15 8y agoInteresting. Do you have more info about that? I heard about web bluetooth, but thought it was still being specified. What peering graphics do you mean?
- olliej 8y agoYou know the patterns you use to peer more or less all IoT devices that have a screen? Or smart watches, etc. Alternatively you could use a code printed on the device, and drive a secret from that. The important thing is that you have to use a non-network side channel first. In this case I assume they’re doing something like an electron app and so their “app” has to communicate of http of some kind, so it already should have app level privileges. If nothing else: if your set up app can install a root certificate then your setup app can do something better than installing a root cert.
- xg15 8y agoMaybe I misunderstand you, but those patterns would always be indirect, would they? Either a device is fully cloud-based, in which case setup consists of giving it the WiFi settings and connecting it to some account - or they communicate locally via e.g. Bluetooth, however then they need some privileged app/helper process to communicate with. But to my knowledge, it's not possible to have it communicate directly with the browser without going through intentionally-scary-and-confusing setup screens or opening security vulnerabilities.
- olliej 8y agoYes, they have to be indirect, that’s the point. If it’s purely cloud based then you’re communicating with the hosts cloud services which can be wrapped in a standard cert and tls connection. In this case they were installing a local server - so you wouldn’t get https issues unless you were also spoofing a domain. In which case it’s correct for you to get warnings (imagine if they inserted your-bank.com -> their localhost server. If you have an app or installer, which they clearly did, then you have other options: * directly insert a leaf certificate (not a root cert) into the platform key store * don’t try to hide that you’re running a local host server. * use an app (this is an option) If I were doing this and couldn’t use Bluetooth, visuals, or sound to make the side channel, I would have the setup program install a leaf certificate derived from something the user can copy from the hardware - serial number or whatever. Or you can have the cloud host provision a leaf cert itself.
- xg15 8y agoWell, 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.