|
|
|
|
|
by PopsiclePete
2050 days ago
|
|
I feel like there's some over-reaction here. You pretty much have to either:
1. allow blanket access to all executables
2. perform some sort of validation/verification Most people are not as technical as the people on this site, and we know that blanket access to all executables is not a great idea. MacOS is not immune to malware. Having executables be signed means the signature has to be checked and the certificate has to be checked to see if it hasn't been revoked. I don't see how to do that without "phoning home" and checking, tbh. I mean yes Apple could enable some expert setting or something for developer/expert types where you can say "trust me I know what I'm doing" but a lot of people who don't know what they're doing will enable that and then malware will run rampant again. It's a shitty situation. But I'm not going to go down the paranoia rabbit-hole of assuming this is done to spy on me. At least not yet. |
|