![]() ![]() ![]() |
|
It looks like Microsoft is trying to address the concerns around Recall in its most recent blog post.
It is made opt-in, and also requires a Windows Hello enrolment to be activated. That way, you need to be physically present - I think they are trying to address the issues around remote exilftration. Also, it has Windows Hello ESS encryption so it is encrypted at rest.
Not going to lie - it still makes me uneasy even with all that.
cmdbit:
It looks like Microsoft is trying to address the concerns around Recall in its most recent blog post.
It is made opt-in, and also requires a Windows Hello enrolment to be activated. That way, you need to be physically present - I think they are trying to address the issues around remote exilftration. Also, it has Windows Hello ESS encryption so it is encrypted at rest.
Not going to lie - it still makes me uneasy even with all that.
With MS's security record, zero chance this isn't going to lead to data leaks on a scale incomprehensible to people currently. That's saying something based on the number of leaks and the size they are now.
At this point you may as well assume your information is out there and hope they don't pick you out of the 140B records that are exposed, to focus on.
Qualcomm is certainly going to be very happy replacing X86 PC/Laptop/Tablet.
With it still being early days re Ai enabling silicon, I suppose the chips will age quickly.
Intel, AMD working on integrating this for sure to pull back that lost socket and $ on the table.
It's more a case of when these architectures get into the low range processors (mass market), vs top end.
Microsoft is taking a hit in putting it out these so clearly up front, but how long before others follow?
Just with more subtle messaging or slower feature creep?
I can see Google/Android going in a similar direction and Apple not leaving the field to Microsoft.
Apples own neural processors on their silicon not there to just looks.
https://www.btimesonline.com/articles/166774/20240608/what-to-expect-at-wwdc-2024-apple-gears-up-for-major-ai-announcements-and-new-features.htm
It's only a matter of time till a security researcher finds an unfixable issue with the new chips that can't be fixed by a microcode update and it cripples the performance of any AI tool because yuou need to put a software patch over the top to filter it.
cmdbit:I am trying to sift out the facts from the opinions.
ezbee: Qualcomm is certainly going to be very happy replacing X86 PC/Laptop/Tablet.
With it still being early days re Ai enabling silicon, I suppose the chips will age quickly.
gehenna:cmdbit:
I am trying to sift out the facts from the opinions.
Based on the direction in this thread, I think the original purpose has been lost. Most of this thread is conjecture reverberating in an echo chamber.
We simply don't have enough information to draw conclusions, particularly since current conclusions are based on a beta insider version.
Scepticism is healthy, being outraged by assumptions isn't.
Many of the worlds most respected security researchers are scathing of the entire project, and breach POC's have *already* been made. Sure, it's beta, but the fact they have hurriedly added security features instead of STARTING with security on a project with the potential for the damage this type of product could create, isn't exactly reassuring.
I’ve just been informed by one of the companies I do some work for that until they are satisfied around the security of MS Recall I’m not to use a Recall enabled system while doing any work for them.
At this stage it’s an informal request, but I expect it will be written formally into some of my future contracts with them. Personally, I’m not surprised and to some point agree with them. In my work there are times when “Secret keys” and Connection strings can and will be visible on my screen. Not to mention other commercially sensitive information.
If my computer is potentially “saving” information I don't want it to save that is then accessed by some third party, is that the same as me breaking my NDA agreements? 🤔
|
![]() ![]() ![]() |