News for hackers. Stuff that matters.
Re:Achieving an open-source implementation of Apple Code Sig... by dwaite on Monday August 08, 2022 @08:58PM (#32392987)
> I think the most common is CI and build automation

Common practice for CI is to actually run tests, though. How would you validate your macOS/iOS builds are functional without still requiring VMs or real hardware?

Re:Achieving an open-source implementation of Apple Code Sig... by 90minuteAPI on Monday August 08, 2022 @09:15PM (#32393101)
If those instances are only for tests/validation it could simplify some overall pipelines quite a bit.
Re:Achieving an open-source implementation of Apple Code Sig... by halbersa on Tuesday August 09, 2022 @10:29AM (#32398496)
We have a pool of MacOS hardware to run tests, and another pool to perform signing. The latter is a security risk so very tightly controlled and locked down. They are a pita to maintain.

Being able to sign on Linux will allow us to re-use the existing signing infrastructure we use for literally every other platform other than MacOS. It'll be more secure and much less maintenance.

Re:Achieving an open-source implementation of Apple Code Sig... by jtdressel on Tuesday August 09, 2022 @08:26AM (#32396909)
You could use this in addition to regular macOS machines. You can run tests from un-trusted branches, without worrying that something will expose the signing keys.

Then after merging, you have a second machine / set of machines that only does signing. It increases the difficulty of an accidental or intentional leakage of your sensitive keys.

(Note: I have not tested this yet)

Re:Achieving an open-source implementation of Apple Code Sig... by the_gipsy on Tuesday August 09, 2022 @01:23AM (#32394438)
That doesn't justify the build part.