Apple Forces the Signing of Applications in MacOS Sequoia 15.1

<img decoding="async" data-attachment-id="732062" data-permalink="https://hackaday.com/2024/11/01/apple-forces-the-signing-of-applications-in-macos-sequoia-15-1/macos_sequoia_unsigned_lock-out_error/" data-orig-file="https://hackaday.com/wp-content/uploads/2024/11/macos_sequoia_unsigned_lock-out_error.png" data-orig-size="520,424" data-comments-opened="1" data-image-meta="{"aperture":"0","credit":"","camera":"","caption":"","created_timestamp":"0","copyright":"","focal_length":"0","iso":"0","shutter_speed":"0","title":"","orientation":"0"}" data-image-title="macos_sequoia_unsigned_lock-out_error" data-image-description data-image-caption="

The dialogue that greets you when you try to open an unsigned application in MacOS Sequoia 15.1.

” data-medium-file=”https://hackaday.com/wp-content/uploads/2024/11/macos_sequoia_unsigned_lock-out_error.png?w=400″ data-large-file=”https://hackaday.com/wp-content/uploads/2024/11/macos_sequoia_unsigned_lock-out_error.png?w=520″ tabindex=”0″ role=”button” class=”size-medium wp-image-732062″ src=”https://hackaday.com/wp-content/uploads/2024/11/macos_sequoia_unsigned_lock-out_error.png?w=400″ alt width=”400″ height=”326″ srcset=”https://hackaday.com/wp-content/uploads/2024/11/macos_sequoia_unsigned_lock-out_error.png 520w, https://hackaday.com/wp-content/uploads/2024/11/macos_sequoia_unsigned_lock-out_error.png?resize=250,204 250w, https://hackaday.com/wp-content/uploads/2024/11/macos_sequoia_unsigned_lock-out_error.png?resize=400,326 400w” sizes=”(max-width: 400px) 100vw, 400px”>

The dialogue that greets you when you try to open an unsigned application in MacOS Sequoia 15.1.

Many MacOS users are probably used by now to the annoyance that comes with unsigned applications, as they require a few extra steps to launch them. This feature is called Gatekeeper and checks for an Apple Developer ID certificate. Starting with MacOS Sequoia 15, the easy bypassing of this feature with e.g. holding Control when clicking the application icon is now no longer an option, with version 15.1 disabling ways to bypass this completely. Not unsurprisingly, this change has caught especially users of open source software like OpenSCAD by surprise, as evidenced by a range of forum posts and GitHub tickets.

The issue of having to sign applications you run on MacOS has been a longstanding point of contention, with HomeBrew applications affected and the looming threat for applications sourced from elsewhere, with OpenSCAD issue ticket #880 from 2014 covering the saga for one OSS project. Now it would seem that to distribute MacOS software you need to have an Apple Developer Program membership, costing $99/year.

So far it appears that this forcing is deliberate on Apple’s side, with the FOSS community still sorting through possible workarounds and the full impact.

Thanks to [Robert Piston] for the tip.

This post was originally published on this site