My understanding is that the Recall database is basically a plaintext local sqlite DB, and the only security measure is that it is stored in a folder for which you need admin rights to access? If so, how is that excusable for a company like Microsoft? I'd say even a weekend hackathon project would implement more security than that?
What further security measures were you imagining? full-disk encryption is now standard in windows 11. So how would you secure the database further from a user with admin rights?
Microsoft Research chief scientist has no issue with Recall
21–30 of 91 posts
Re: Microsoft Research chief scientist has no issue with Recall
#22We've launched a FOSS alternative with OpenRecall https://github.com/openrecall/openrecall to (hopefully) work towards addressing some of the concerns people have with Windows Recall. We think it could be a useful feature but it must be (1) fully auditable/open source (2) using open source local models (3) focused on privacy/security and (4) hardware/OS independent. We're working out the roadmap currently so any feed…
It should be either:
- browser only and semantically understand and hide sensitive information like password fields (or even all input fields)
- or capture stuff from the display server and make it configurable which applications should be ignored (e.g. password manager), and even prompt with each newly opened window if the user wants to remember that session
...and that's just the basics, if we go into details I'm sure there's much more to it.
Re: Microsoft Research chief scientist has no issue with Recall
#23Earlier quoted context omitted.
What further security measures were you imagining? full-disk encryption is now standard in windows 11. So how would you secure the database further from a user with admin rights?
At least encrypt the database records, so if someone steals your sqlite data they don't automatically know what you were doing on your pc.
Re: Microsoft Research chief scientist has no issue with Recall
#24Earlier quoted context omitted.
What further security measures were you imagining? full-disk encryption is now standard in windows 11. So how would you secure the database further from a user with admin rights?
At least encrypt the database records, so if someone steals your sqlite data they don't automatically know what you were doing on your pc.
Re: Microsoft Research chief scientist has no issue with Recall
#25Earlier quoted context omitted.
What further security measures were you imagining? full-disk encryption is now standard in windows 11. So how would you secure the database further from a user with admin rights?
At least encrypt the database records, so if someone steals your sqlite data they don't automatically know what you were doing on your pc.
Re: Microsoft Research chief scientist has no issue with Recall
#26Privacy/security issues aside. It’s a really freaken useful tool that I’m already missing on other devices.
Re: Microsoft Research chief scientist has no issue with Recall
#27Re: Microsoft Research chief scientist has no issue with Recall
#28Earlier quoted context omitted.
where did you hear that? > Snapshots are encrypted by Device Encryption or BitLocker, which are enabled by default on Windows 11. Recall doesn't share snapshots with other users that are signed into Windows on the same device. Microsoft can't access or view the snapshots. You can delete your snapshots at any time by going to Settings > Privacy & security > Recall & snapshots on your PC. source: https://support.micros…
Some excerpts from https://doublepulsar.com/recall-stealing-everything-youve-ev... : ---------- Q. So how does it work? A. Every few seconds, screenshots are taken. These are automatically OCR’d by Azure AI, running on your device, and written into an SQLite database in the user’s folder. This database file has a record of everything you’ve ever viewed on your PC in plain text. OCR is a process of looking an image, a…
Re: Microsoft Research chief scientist has no issue with Recall
#29And by hilarious, I mean bad. Screenshots of PHI? Sweet as, just chuck them in an SQLite DB, no worries there.