When Microsoft CEO Satya Nadella revealed the new Windows AI tool that can answer questions about your web browsing and laptop use, he said one of the “magical” things about it was that the data doesn’t leave your laptop; the Windows Recall system takes screenshots of your activity every five seconds and saves them on the device. But security experts say that data may not stay there for long.

Two weeks ahead of Recall’s launch on new Copilot+ PCs on June 18, security researchers have demonstrated how preview versions of the tool store the screenshots in an unencrypted database. The researchers say the data could easily be hoovered up by an attacker. And now, in a warning about how Recall could be abused by criminal hackers, Alex Hagenah, a cybersecurity strategist and ethical hacker, has released a demo tool that can automatically extract and display everything Recall records on a laptop.

Dubbed TotalRecall—yes, after the 1990 sci-fi film—the tool can pull all the information that Recall saves into its main database on a Windows laptop. “The database is unencrypted. It’s all plain text,” Hagenah says.⁩ Since Microsoft revealed Recall in mid-May, security researchers have repeatedly compared it to spyware or stalkerware that can track everything you do on your device. “It’s a Trojan 2.0 really, built in,” Hagenah says, adding that he built TotalRecall—which he’s releasing on GitHub—in order to show what is possible and to encourage Microsoft to make changes before Recall fully launches.

  • slimarev92@lemmy.world
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    1
    ·
    5 months ago

    Why on earth aren’t they encrypting the database? It could have adressed much of the criticism but they just decided to leave the whole thing completely unprotected.

        • esc27@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          5 months ago

          Yep. Trying to maintain a consistent startmenu for computer labs with Windows 11 is annoying.

          The layout is stored in an encrypted file that cannot be editted directly. You have to manually setup the start menu on one profile then copy the file to all the others. This works fine for intial deployments, but is a massive pain if you need to add any other apps later.

          The old powershell commandlet for importing layouts does not work in Win11. The old group policy settings don’t work either. The actual DLL calls used by the end user to manually configuring the start menu are deliberatly coded to prevent being called from a script.

          It is freaky how much work Microsoft has done to prevent scripting changes to the start menu.

          The only officially supported method for an IT department to manage the start menu is intune, but microsoft’s device licensing for intune is a mess out folks have yet to figure out.

    • BaroqueInMind@lemmy.one
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      2
      ·
      5 months ago

      Likely because there was too much CPU overhead decrypting and having the LLM query the Recall image database all dynamically

    • Morphit @feddit.uk
      link
      fedilink
      English
      arrow-up
      5
      ·
      5 months ago

      It requires full disk encryption doesn’t it? If someone already has access to your account then they can access this data the same way you can. The new issue here is that this silos a load of private data in one easy to grab location. Users would have to set up the filters perfectly to prevent recall capturing anything more sensitive than what’s already accessible to their account. This is in a world where many users are probably storing their passwords in a Word document on the desktop.

    • Katana314@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      5 months ago

      It could be that anything you encrypt has to have its encryption key in some place inaccessible to these same hacker tools. If your computer uses Bitlocker, for instance, you need to enter a 6-digit code each time you turn it on.

      Best guess, they had such a high expectation of “convenience” for this feature that they couldn’t justify any kind of security key. Which is still a dumb explanation, obviously.