3 ms·
Most of this problem is solved by not hiding the trust model. Do you want an phone where you trust Apple/Google/3rd party to make a "malware or not" decision?
by zdw 1y ago
Most of this problem is solved by not hiding the trust model.
Do you want an phone where you trust Apple/Google/3rd party to make a "malware or not" decision? Or one where all that is turned off and you can do whatever? Go right ahead in either case - you control the trust, rather than it being made for you by the platform vendor.
Similarly, we have certificate infrastructure where the TLS roots are owned by a small number of people. These are generally trusted, but some people/organizations edit them down (ex: removing roots from state actors deemed untrustworthy). But it's hidden, and generally a lot of choices.
Even linux distros, you pick which package signing keys you trust.
And Docker/K8s... oh wait, there's no default keys and containers remain being developer's puke bags in most cases, and the repos are rugpulled by corporations regularly...
- deleted 1y ago[deleted]
- Nursie 1y agoI look forward to you explaining all that to my elderly mother. Once you’ve explained the difference between Google and “the internet”, you may stand a chance. I wish you luck, I’ve been trying that for a while. BRB, heading out for popcorn.
- error503 1y agoThey don't even need to know it is a thing that exists. The defaults (ie. the status quo of implied trust in the OS vendor) are fine for this type of user.
- Nursie 1y agoSure. Now how are we going to stop them being talked into changing that by scammers, given that we’re not even explaining what that does?