Sometimes it won’t let you even get to that step without going into the settings and finding a secret security notification that it blocked it from opening
What version are you running? I just tried on Ventura, worked fine on both a .dmg package and some terminal script, both unsigned, and both would need the settings thing if I simply double clicked to open. You still get a prompt, but you have an “open anyways” option.
I’m on the latest version right now, but can’t remember a time I’ve actually installed something on this version. On at least the previous version I believe I had a mix of annoying and the “open anyways” prompt, and then before that just annoyance. I can’t remember exactly what I was installing off the top of my head though, sorry
I mean, macOS has a lot of issues but the one hoop needed to run any unsigned app is “right-click app icon, click open”.
OMG thanks.
I think I actually knew this at some point but somehow it completely slipped my mind.
Sometimes it won’t let you even get to that step without going into the settings and finding a secret security notification that it blocked it from opening
What version are you running? I just tried on Ventura, worked fine on both a .dmg package and some terminal script, both unsigned, and both would need the settings thing if I simply double clicked to open. You still get a prompt, but you have an “open anyways” option.
I’m on the latest version right now, but can’t remember a time I’ve actually installed something on this version. On at least the previous version I believe I had a mix of annoying and the “open anyways” prompt, and then before that just annoyance. I can’t remember exactly what I was installing off the top of my head though, sorry
Yeah, and in rare instances, you’ll need to take the app/binary out from the quarantine
I guess that is true, yes. I do think it’s generally a good thing that they’re locking down specific permissions like that though.