![]() |
|
![]() |
| > Heres something I just don't get.
> And then someone goes and invents Recall Maybe you should read about the history of Microsoft, especially about its security. But people forget easily. |
![]() |
| > that little thought has gone into privacy or security.
I think the thought is proportional to the amount of thought a non-tech customer will put into it. Nobody seems to care about or understands privacy these days. Everyone knows they're being tracked everywhere they go physically and on the web. People use their real names, address, etc for every junk service they sign up for, without seeing any reason not to. If you tell people that their TV is tracking and taking screenshots of what they watch [1], they say "yeah, Netflix knows too". It's literally, "how it's always been" for any non tech person under 30. [1] https://themarkup.org/privacy/2023/12/12/your-smart-tv-knows... |
![]() |
| I think it’s a good point - these are still privacy issues, and being fatigued with the impossibility of defending privacy is indication of a power imbalance, not an acceptable default for humanity. |
![]() |
| Right, the pervasivenes today is much higher. But marketers/advertisers have always hoovered up and exploited as much information as was technically possible. That attitude isn't new. |
![]() |
| I mean, you can't even install Windows 10 without it telling you several times that unless you opt out (again and again), it's going to send just about anything you do to Microsoft… |
![]() |
| Perhaps. A key difference though - history files can include the individual pages I requested from the same host. Right now I have like 50 entries for the various posts I read just from HackerNews, all as separate line items etc etc.
In the case of the phone, one simply sees recipient of call, duration etc, regardless of how much information was exchanged. The phone I'm calling is arguably analogous to the server I request a page from, in the metadata context. I'd argue browser history is significantly richer in some regards due to this. It's not unheard of for user identifiers to appear in URL paths either - try visiting https://news.ycombinator.com/user?id= |
![]() |
| Yeah, but in theory Recall doesn't upload anything either, which is why it's analogous. And in fact Chrome does upload passwords, and they're not even E2E encrpyted in the default configuration. |
![]() |
| > It's interesting to compare this to the Chrome/Safari/Edge browsing history, which is stored in an unencrypted SQLite database ...
Recall seems to be storing its info locally in an unencrypted SQLite database as well. At least, that's according to the instructions here on how to access and view the contents: https://www.heise.de/en/news/First-experiences-with-Recall-9... From the submitted article, it seems like Microsoft will change/secure the access (and maybe storage) in some way, though there's no details on the specifics. |
![]() |
| Extensions can simply download and update their own code, eg by loading new stuff from localStorage.
I have seen Metamask update itself randomly, and it has access to read every website |
![]() |
| I did read the article. The person I'm replying to claims the entire debate was "uninformed hysteria", which means they thought the previous security model already required admin. |
![]() |
| If an attacker got root with recall they might not need to wait the user to type their password and risk detection. The information they want to know might be already in the recall database. |
![]() |
| If you had screen recording on by default you’d run out of disk space pretty quick.
MS just did what every other micromanagement company did and took screenshots every second or so. |
![]() |
| > Without Recall, an attacker needs to get a program to stay resident in memory to log keystrokes, screen contents, etc
Or it could just steal your cookies which are out there in the open. |
![]() |
| This is all moot anyway because Microsoft has already said they are now going to encrypt everything behind Windows Hello making it as secure as my password manager. |
![]() |
| That's old information. This is how Microsoft is intending to change Recall based on these criticisms:
Microsoft will also require Windows Hello to enable Recall, so you’ll either authenticate with your face, fingerprint, or using a PIN. “In addition, proof of presence is also required to view your timeline and search in Recall,” says Davuluri, so someone won’t be able to start searching through your timeline without authenticating first. This authentication will also apply to the data protection around the snapshots that Recall creates. “We are adding additional layers of data protection including ‘just in time’ decryption protected by Windows Hello Enhanced Sign-in Security (ESS) so Recall snapshots will only be decrypted and accessible when the user authenticates,” explains Davuluri. “In addition, we encrypted the search index database.” https://www.theverge.com/2024/6/7/24173499/microsoft-windows... |
![]() |
| Well it is "old" since the article is about Microsoft's blog post where they discuss all these changes!
https://blogs.windows.com/windowsexperience/2024/06/07/updat... > It remains baffling and worrisome that it took a public outcry for them to implement what sounds like a baseline level of acceptable protection. It's possible this was the intention all along but as a early-beta feature this was just the MVP. The reason it was rolled out to early testers at all was to get feedback. |
![]() |
| I bet there are a trillion companies and governments who want to know what all of their employees are doing every second of the workday. compliance won't stop them from trying. |
![]() |
| On LinkedIn someone in my network pointed out that, apart from the security and privacy disaster, the name Recall was a bad choice because of negative events like product recall. |
![]() |
| You can also define software restriction policies to do similar things.
It id what SRP's are for (but yes, I would not put it past them to disable anything targeting OneDrive). |
![]() |
| That is truly insidious, but FWIW, you don't need to abandon Windows entirely because of this. There are ways of creating a custom Windows installation disk that removes OneDrive, along with other bloatware, spyware, and pretty much anything else you don't like. Look into tools such as Tiny11 Builder, MSMG Toolkit, NTLite, etc. This is a decent guide[1] for setting all of this up.
The process is quite tedious and takes a few hours, but in the end you end up with a personalized version of Windows, without any of the garbage. You still need to be vigilant of Windows Update undoing some of this, but you can also disable it altogether and manually cherry pick the updates you want to install. It's insane that Microsoft is building such a user hostile OS that forces users to resort to this, but if you absolutely must use it, the experience after doing the above is not so bad. I've been running a custom install of Windows 11 for about a year now without any issues. [1]: https://www.tomshardware.com/how-to/create-custom-windows-11... |
![]() |
| And I can almost guarentee you it will magically all turn itself back on/reinstall itself eventually after the OS force updates/reboots itself in the not too distant future. |
![]() |
| you just have to use dopus as a file explorer replacement and just use dropbox (with cryptomator of course...) to yield (in most respects) best in class file management and sync |
![]() |
| Always set Windows up with a local account to avoid this nonsense. Used to be relatively straightforward in Windows 10, but MS made it a lot harder to dodge in 11. |
And then someone goes and invents Recall. This is not the work of a lone engineer and a principal PM fishing for Impact or whatever they call success at Microsoft. This had to have gone through multiple levels of review. Microsoft PMs, CVPs, their corpo legal people, marketing approval. And yet no one stopped to say, "wait, this could blow up in our faces"?