• AllNewTypeFace@leminal.space
    link
    fedilink
    English
    arrow-up
    0
    ·
    8 months ago

    I wouldn’t be surprised if someone reverse-engineers the protocol and codes up their own replacement backend as a one-file Python script in a weekend.

    • IphtashuFitz@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      8 months ago

      That truly depends on how secure Ecobee made it… I’ve seen some smart devices that use SSL (https) for all communication and do some sort of certificate authentication, making it virtually impossible to decrypt its communication protocol without a valid private key…

      Having said that, it’d be nice if Ecobee took the initiative and opened up these older devices, if they could do so without comprising the security of all their others.

      • AllNewTypeFace@leminal.space
        link
        fedilink
        English
        arrow-up
        0
        ·
        8 months ago

        Is the firmware enclosed in a SOC with no way of reading/extracting it? If not, if all else fails, someone will extract it and dissect it with Ghidra or something, extracting whatever encryption keys are needed. If so, and there aren’t any documented side-channel attacks for reading the firmware from this SOC, if firmware updates exist, they too constitute an attack surface. (They probably would be encrypted, but how strongly?)