CURA unsigned on macOS?

Get answers & advice for all of your 3D printing & Free Software needs here!
Post Reply
Posts: 1
Joined: Thu Feb 21, 2019 2:20 pm

CURA unsigned on macOS?

Post by fablabRUC » Thu Feb 21, 2019 2:23 pm


I was wondering why CURA remains unsigned software on macOS? I can't imagine it being a large problem to overcome?

Posts: 10
Joined: Sun Feb 18, 2018 5:43 pm

Re: CURA unsigned on macOS?

Post by mnemosyne » Wed Mar 13, 2019 9:46 am

I have been wondering the same thing.

User avatar
Posts: 38
Joined: Fri Nov 14, 2014 12:25 pm

Re: CURA unsigned on macOS?

Post by 3dRiffs » Thu Mar 28, 2019 8:43 am

I'm sure it's because lulzbot insists on only using foss software for everything, signing requires using Xcode, and there's terms in the license they won't agree to.

I've been trying to get them to change the install instructions for years, as their method disables important security features in OS X. The proper method, which only bypasses gatekeeper for the application itself (and is only required once) is to right/control click on the application, then choose open from the pop up menu. Once you approve the warning, the os will remember the exception and you won't have to do it again.

Posts: 37
Joined: Sun Jul 19, 2015 7:56 am
Location: Loveland CO

Re: CURA unsigned on macOS?

Post by idcrook » Sat Aug 24, 2019 5:04 pm

macOS 10.15 Catalina also requires apps to be notarized. This is a process in addition to signing the app binaries. ... stribution
Beginning in macOS 10.14.5, all new or updated kernel extensions and all software from developers new to distributing with Developer ID must be notarized in order to run.

Beginning in macOS 10.15, notarization is required by default for all software.

Post Reply