4 ms·

In my case you actually do know that the vendor is using the protocol. You would have to be running the protocol on (in this example) your iPhone in order to ta

by nbadg 10y ago

In my case you actually do know that the vendor is using the protocol. You would have to be running the protocol on (in this example) your iPhone in order to talk to it. Everything is client-side verified and enforced by encryption. You wouldn't have any guarantee that the garage door opener isn't also running a separate web connection in the background, but arguably unless you're actively monitoring your LAN (or just plain radio) traffic you don't have that anyways. Put a different way, you can't prevent your manufacturer from, for example, adding a SIM card and wireless connection to your garage door opener. At some point you have to trust them.

DougN7 10y ago
When you say I'd have to be running the protocol, wouldn't I really be running their garage door opener app? In other words, how do I know your protocol is being used?
- nbadg 10y ago
  If they were using the protocol, they have two options: 1. Roll their own implementation (highly discouraged). Increase their development burden. Introduce higher maintenance burden. Slightly more flexibility for app deployment. And run the risk of my company disallowing interoperable embedded commercial implementations out of security concerns for the users. Basically, at this point the company is better off not using the protocol. 2. Use our implementation (Hypergolix). Massively decrease development and maintenance burden. They now have an install dependency, though, so distribution is a bit more complicated. Significant reduction in time and money invested in the app. The critical point is this: with option 1, you're correct in that you don't know the protocol is in use, but it's extremely likely that they wouldn't be using it here, nor advertise that they were. With option two, you know that they are using it, because you have to manually install the application to run the protocol.
  - DougN7 10y ago
    With #2 do I know they are using your additional install? Would your app indicate their app was a registered client and was sending commands through it?
    - nbadg 10y ago
      It certainly could, as it has full knowledge of what's connected. That's quite a ways down the road though; for now we're focusing on Razpi <-> computer. Mobile deployment is much more complicated (also a much larger market though).

by nbadg 10y ago

DougN7 10y ago

When you say I'd have to be running the protocol, wouldn't I really be running their garage door opener app? In other words, how do I know your protocol is being used?

nbadg 10y ago
If they were using the protocol, they have two options: 1. Roll their own implementation (highly discouraged). Increase their development burden. Introduce higher maintenance burden. Slightly more flexibility for app deployment. And run the risk of my company disallowing interoperable embedded commercial implementations out of security concerns for the users. Basically, at this point the company is better off not using the protocol. 2. Use our implementation (Hypergolix). Massively decrease development and maintenance burden. They now have an install dependency, though, so distribution is a bit more complicated. Significant reduction in time and money invested in the app. The critical point is this: with option 1, you're correct in that you don't know the protocol is in use, but it's extremely likely that they wouldn't be using it here, nor advertise that they were. With option two, you know that they are using it, because you have to manually install the application to run the protocol.
- DougN7 10y ago
  With #2 do I know they are using your additional install? Would your app indicate their app was a registered client and was sending commands through it?
  - nbadg 10y ago
    It certainly could, as it has full knowledge of what's connected. That's quite a ways down the road though; for now we're focusing on Razpi <-> computer. Mobile deployment is much more complicated (also a much larger market though).