News for hackers. Stuff that matters.
Re:Apple's 15% Deflection Tactic by dcchambers on Wednesday November 18, 2020 @10:21PM (#25145859)
I found some more info:

https://eclecticlight.co/2020/08/22/apple-silicon-macs-will-...

Seems like only binaries compiles to run natively on ARM will require signatures. Still seems like its going to introduce some inconvenience for developers/power-users.

Re:Apple's 15% Deflection Tactic by winkeltripel on Wednesday November 18, 2020 @11:43PM (#25146301)
Signing bins as part of your build chain seems easy to me.
Re:Apple's 15% Deflection Tactic by onion2k on Thursday November 19, 2020 @02:29AM (#25147069)
Don't self-signed apps expire after a week? You'd need to distribute a new build every week for people to continue to use your app. That's not a major hassle if you're just using your own code, but if you want to distribute something to other people it quickly becomes very problematic.
Re:Apple's 15% Deflection Tactic by saagarjha on Thursday November 19, 2020 @05:24AM (#25148017)
You can "sign" your binary without any identity associated with it and macOS will let it run. There is no time limit on those.
Re:Apple's 15% Deflection Tactic by dcchambers on Thursday November 19, 2020 @09:11AM (#25149600)
I agree - for commercial development its a trivial step. But it's yet another barrier to entry for students and people that just want to hack on their own computer at will.

It's also a potentially dangerous first step towards forcing new versions of MacOS to only run code from verified developers - those that pay Apple. Again, trivial for commericial development, but a major issue for non-commercial use.