• jaschen306@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      4 hours ago

      This is great, but outside the security aspects of things. What else can this firmware do that I can’t with say, the roborock? Am I giving up functions?

      • papertowels@mander.xyz
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 hours ago

        Unfortunately you’ll have to do your own research, I only know this exists and have never used it because my vacuum is incompatible.

  • Nightsoul@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    13 hours ago

    I mean, this has been known about for pretty much all smart vacuums.

    But who the fuck is going to use the layout of your house for anything?

  • zalgotext@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    6
    ·
    20 hours ago

    If you have a robot vacuum, and the robot vacuum makes a persistent map (as opposed to the older “dumber” models that just bounce around randomly), they all send that map back to some remote server. In fact, most of those robots won’t even enable the mapping feature unless they’re connected to the Internet (which is absolute bullshit considering most of those robots generate, process, and store that map locally, so there’s literally no reason to send it off somewhere).

    So your options are to just use the robot without ever connecting it to the Internet and be happy with the reduced featureset, root the robot and install Valetudo on it, or just vacuum manually. But until manufacturers are forced to let us actually own the smart devices they sell is, under no circumstances should you ever let one touch the Internet.

    • Auli@lemmy.ca
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      1
      ·
      edit-2
      22 hours ago

      My home assistant isn’t spying on me. My Zwave devices are not spying.

        • ijustliketrains@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          ·
          17 hours ago

          Home Assistant is open source and self-hosted and doesn’t require internet to operate. The z-wave devices connect directly to the device running Home Assistant. If you want Home Assistant to be private it absolutely can be.

  • Captain Aggravated@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    4
    ·
    20 hours ago

    I’ve been looking into robotic lawnmowers, and they’re basically the same. The more primitive ones have a hall effect sensor under their snout feeling for a wire you bury around the edge of your yard, and do the “go until you hit something, turn a random amount, repeat until low battery, follow perimeter to dock” or they require phoning home in some way, shape or form.

    Meanwhile, some guy’s got an open source system that runs on a Raspberry Pi on the mower itself.

    I guess I’m willing to believe that some of the LIDAR or camera-only guided mowers need some serious processing power to create the maps they use for guidance around the yard, and that’s more practical to do on the company’s servers than on the device itself…except not really; we’ve got decently powerful ARM SoCs that don’t cost much, don’t take a lot of power to run, and can do that job. The reality is, you can’t get a pedometer app for a smart phone that doesn’t broadcast sensor telemetry to two continents these days.

  • 87Six@lemmy.world
    link
    fedilink
    English
    arrow-up
    147
    ·
    2 days ago

    Since I dont see it mentioned, the company is

    iLife

    iLife makes vacuums that map your house and can be remote controlled

    Just so we are clear. You should all up your name and shame game.

    • Basic Glitch@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      6
      ·
      edit-2
      1 day ago

      Worst case, it’s sold to ICE or some other fascist regime.

      Every single government that has a contract with Palantir for Gotham or even whatever the fuck they’re doing with the UK NHS data, is reason enough to know this kind of shit is a bad idea. The entire existence of Palantir makes this kind of shit a bad idea by default.

      Even if they’re not using lavender or where’s daddy (yet), I do not want them to have a detailed layout of my home, in addition to all the other information already being collected.

      If the day comes when any government needs to crush civil unrest, Palantir gives them an easy button to weaponize your data against you.

  • lechekaflan@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    1
    ·
    1 day ago

    I remember about news of some Israeli intelligence operatives who jogged around their HQ only to be outed by their tracks on Strava.

  • Basic Glitch@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    33
    ·
    2 days ago

    “Someone — or something — had remotely issued a kill command,” he wrote.

    “I reversed the script change and rebooted the device,” he wrote. “It came back to life instantly. They hadn’t merely incorporated a remote control feature. They had used it to permanently disable my device.”

    In short, he said, the company that made the device had “the power to remotely disable devices, and used it against me for blocking their data collection… Whether it was intentional punishment or automated enforcement of ‘compliance,’ the result was the same: a consumer device had turned on its owner.”

  • ByteOnBikes@discuss.online
    link
    fedilink
    English
    arrow-up
    71
    ·
    2 days ago

    In addition, Narayanan says he uncovered a suspicious line of code broadcasted from the company to the vacuum, timestamped to the exact moment it stopped working. “Someone — or something — had remotely issued a kill command,” he wrote.

    “I reversed the script change and rebooted the device,” he wrote. “It came back to life instantly. They hadn’t merely incorporated a remote control feature. They had used it to permanently disable my device.”

    In short, he said, the company that made the device had “the power to remotely disable devices, and used it against me for blocking their data collection… Whether it was intentional punishment or automated enforcement of ‘compliance,’ the result was the same: a consumer device had turned on its owner.”

    They kill switched it remotely. Yikes.

    • muusemuuse@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      10
      ·
      2 days ago

      All IoT devices do this to keep you from blocking their data collection. They won’t work reliably without a regular ping home. They lock up if they can’t phone home frequently enough.

      • Auli@lemmy.ca
        link
        fedilink
        English
        arrow-up
        1
        ·
        22 hours ago

        Haven’t had one yet. Block all IOT devices from internet all work fine.

    • Evotech@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      arrow-down
      1
      ·
      2 days ago

      More likely it killed itself after not being in contact with home base. Since it worked fine elsewhere

  • Steve Dice@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    18
    ·
    2 days ago

    I used to be on a mailing list where American companies offered money to people in the third world for menial manual tasks. Like sending pictures of random crap from different angles and such. One time I got an email offering 4 of these things and $100 and all I had to do was put one of them in my home and use it for a week and give the other 3 away. Goes without saying they’re clearly a privacy nightmare.

  • Regna@lemmy.world
    link
    fedilink
    English
    arrow-up
    266
    arrow-down
    1
    ·
    edit-2
    2 days ago

    At first I thought ”Well, duh!”, but the manufacturer having a remote kill switch when he network blocked his vacuum from sharing his home map data with them, as well as unprotected root access when connecting to the vacuum… urgh.

    The engineer says he stopped the device from broadcasting data, though kept the other network traffic — like firmware updates — running like usual. The vacuum kept cleaning for a few days after, until early one morning when it refused to boot up.

    After reverse engineering the vacuum, a painstaking process which included reprinting the devices’ circuit boards and testing its sensors, he found something horrifying: Android Debug Bridge, a program for installing and debugging apps on devices, was “wide open” to the world. “In seconds, I had full root access. No hacks, no exploits. Just plug and play,” Narayanan said.

    • justsomeguy@lemmy.world
      link
      fedilink
      English
      arrow-up
      131
      arrow-down
      1
      ·
      2 days ago

      All crappy IoT devices ever made. They aren’t used in bot nets all the time because hackers like the challenge of hacking them so much. Security simply isn’t a priority.

    • Monument@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      51
      ·
      edit-2
      2 days ago

      A few years ago I noticed an annoyance with a soundbar I had. After allowing it onto my WiFi network so we could stream music to it, it still broadcast the setup WiFi network.

      While dorking around one day, I ran a port scan on my network and the soundbar reported port 22 (ssh) was open. I was able to log in as root and no password.
      After a moment of “huh, that’s terrible security.” I connected to the (publicly open) setup network, ssh’d in, and copied the wpa_supplicant.conf file from the device to verify it had my WiFi info available to anyone with at least my mediocre skill level. I then factory reset the device, never to entrust it with any credentials again.

      • KazuyaDarklight@lemmy.world
        link
        fedilink
        English
        arrow-up
        93
        ·
        2 days ago

        Tend to agree, security is always the goal but if someone is in my house hacking my vacuum, I have bigger issues. The no-notice remote kill is the bigger issue to me.

        • subignition@fedia.io
          link
          fedilink
          arrow-up
          13
          ·
          2 days ago

          The much bigger concern is that the pathway used to send the remote kill command could very easily be utilized by nefarious actors.

        • Riskable@programming.dev
          link
          fedilink
          English
          arrow-up
          45
          ·
          2 days ago

          NO! It’syour device, you should have root! The fact that the manufacturer gives their product owners root is a good thing, not bad!

          I will die on this fucking hill.

            • JustEnoughDucks@feddit.nl
              link
              fedilink
              English
              arrow-up
              3
              ·
              1 day ago

              But on this threat model? Why would it not be good?

              It has to physically accessed on the PCB itself from what I gather.

              There are 2 “threats” from what I see:

              • someone at the distribution facility pops it open and has the know how to install malware on it (very very unlikely)

              • someone breaks into your home unnoticed and has the time to carefully take apart your vacuum and upload pre-prepared malware instead of just sticking an IP camera somewhere. If this actually happens, the owner has much much bigger problems and the vacuum is the least of their worries.

              The homeowner is the other person that can access it and it is a big feature in that case.

  • Sam_Bass@lemmy.world
    link
    fedilink
    English
    arrow-up
    15
    ·
    1 day ago

    Yeah that issue has been around for at least a couple years now. Luckily my robovac doesn’t have WiFi or bluetooth