- 25comments
- 216comments
- 121comments
- 8comments
- 16comments
- 62comments
- 120comments
- 455comments
- 145comments
- 11comments
- 15comments
- 296comments
- 80comments
- —discuss
- 2comments
- 8comments
- 375comments
- 472comments
- 36comments
- 3comments
- 382comments
- 50comments
- 40comments
- 36comments
- 141comments
- 357comments
- 30comments
- 430comments
- 194comments
- 35comments
Who in their right mind would install a Meta AI with near admin privileges?
We all fear the true answer to that question.
almost every normal person
Normally I’m not one to blame the victims but, uh, yeah who in the world is dumb enough to trust Meta at this point?
most people don't know or care what "admin privileges" even means, or why they wouldn't want ai to have them.
and, as baffling as it is to many of us here, a huge portion of people literally do not care at all when their digital data gets sent to meta/google/whoever.
Almost everyone who is struggling with AI insecurity and is afraid of being left behind
I'm confused what the vulnerability is. Does macOS have some specific function for protecting key material, that it's unexpected that if you execute user-privileged code locally, outside of a sandbox, it gets full read access?
Yeah macOS security is capability based rather than purely identity based. So if you don't pass the required entitlements to an application then it cannot do stuff like read from the system keychain even if its running as your user.
A zero day? Of course it does. It likely has many. Given the history of software, it's impossible to think it wouldn't.
Maybe they should have spent the money used to buy its stupid name from a band on additional testing instead.
Did the band end up getting money for that?
Not sure these guys realize that the quality and latency of those Apple services in MacOS is way lower than SOTA and not too many people use them because of that…