3 ms·
I can't think of a single (non-malicious) rational cause for requiring code signing by default and making the requirement impossible for the user to disable. W
by Wowfunhappy 7y ago
I can't think of a single (non-malicious) rational cause for requiring code signing by default and making the requirement impossible for the user to disable.
We're talking about what Apple could be planning that would violate the GPLv3. As long as the signing can be disabled by the user, there shouldn't be a GPLv3 violation.
- Someone 7y agoIf there were a simple checkbox in the OS to disable SIP, I would expect zillions of ‘nice’ add-ons would ship with instructions on how to disable it. I also expect zillions of helpful nieces/nephews would flip that checkbox for their uncles/aunts, and, accidentally or on purpose, leave it that way. Even if that isn’t true, making it harder for malware to flip that flag already is a rational reason to implement it this way.
- Wowfunhappy 7y agoI have zero issues with how SIP is currently implemented. It's just hard enough to turn off to protect people, without being overly annoying. I do worry very much about SIP becoming impossible to disable some day. Don't ban knives because people might cut themselves.