MacOS Sequoia -- "Allow Apps from Anywhere" (or GateKeeper) has been modified..

There’s a safer way to open an app without risking hacks, cracks, malware, or ransomware.

1. Press Shift + click to Open the app.

2. When prompted about possible malware, press Done instead of Send To Trash.

3. Go to System Settings > Privacy and Security.

4. Scroll down and click “Open Anyway” in the window right of the sidebar.

5. Follow the prompts to allow the app to open.

This method is different from before Sequoia 15.1.1. Instead of shift-clicking the app, click Open, then click Open Anyway. This is the same thing, but the “Open Anyway” button is now in System Settings > Privacy and Security.

I called Apple Care for help, and this is what they told me. It worked perfectly.

Remember, if you’re opening an app, ensure the app’s source is trustworthy.

I hope this helps someone out there in cyberspace.

sadly my Allow Applications from drop down does not have "Anywhere". Any ideas why? Anyone. Please God

ToddToddRoy wrote:

sadly my Allow Applications from drop down does not have "Anywhere". Any ideas why? Anyone. Please God

You don't want that. As mentioned earlier, it's a huge security hole.

After trying a few times sudo spctl --master-disable, need you re-launch the window of terminal and system setting finaily it works. Anywhere is showing on the Security.

For those that do not wish to tinker with the terminal, just use Onyx from titanium software...

It is a multifunction utility that has been around since the days of Jaguar and it works with the latest Sequoia.

You can set various "hidden" mac settings, set Finder patameters and so much more but most importantly disable gatekeeper with just one toggle.

I am not affiliated with Onyx in any shape or form, just a happy user since Mac OS X 10.2, so here is the download page:

Onyx

If I "don't want that", please explain how Apple expects me to run my own console apps I have written? I don't want to use the store for my own apps nor am I a "known" developer. FWIW I did the above procedure, enabled allow from anywhere and still it prevents my basic apps from running. Honestly this Macbook Pro is becoming more and more of an expensive paperweight. This isn't about security it's about monopoly. I long for the day Asahi or even Windows runs natively on my hw. I've never had bigger remorse.

This recent I've been using Macs since 1988 and I've yet to be attacked with anything. Except paranoia. Macs used to be the computer for the rest of us. Now it's starting to feel like the computer that I.T. lets us have access to.

[Edited by Moderator]

djconns13 wrote:

I'll give y'all a far easier way round all this nonsense of typing in commands in terminal and all that nonsense, open privacy and security, in the search box type "open download" or open. It will pop up gatekeeper, click it, then under security you have the option to open and run your file from allow applicationsfrom anywhere. Once done, disable it if youre worried about security! Simples

By default, that option hasn't existed since at least Sonoma, maybe earlier.

Getting it back in the menu requires "commands in terminal and all that nonsense."

MacOS is designed by Apple, and is therefore essentially free of bugs, requires little maintenance and is not susceptible to malware. If you are encountering issues it follows that you are obviously doing something wrong.

@jimfromgowanda I am fully aware of who makes Apple macOS. It's kinda in the name. I know my way around Macs and have done for a very long time, all the way back to os 9.1, so pre unix.

Apples paranoia and control is getting out of control. Things like this should be a simple fix but they keep messing with the structure of the OS and how to be able to deal with security issues. Anyway, that's a different argument for a different day.

jamesmcsparron wrote:

I didn't get this randomly. It came off the back of a lorry with the App, if you know what I mean?

I do not.

And it worked on on my Macbook. I then deleted it's profile when I was done with my dirty dealings. All for the sake of learning I should add. No silver crossed my palm etc etc.

But given that you don't know why it can't possibly work, you shouldn't be recommend it to other people.

Hint: ukdesigner's last reply explicitly says why it doesn't work.

innerspace3, as is typical of an Apple Support Communities Discussion that has grown into several pages over several months this one has gone off the rails reducing it to little more than noise. Its originator resolved his or her problem a while ago and hasn't been back since. For that reason and others I recommend that you start your own Discussion. To do that click the Ask the Community link above.

Writing an effective Apple Support Communities question - Apple Community

Personally I don't believe your particular concern is related to the subject of this Discussion.

Dario Buttazzo wrote:

Unfortunately this is incorrect. Gatekeeper in fact prevents me from opening code I wrote, and the problem is not elsewhere. For every new terminal executable, I need to open Settings and allow that single app, and then enter my password. For someone that writes code regularly this is unsustainable. I agree that disabling security settings is not a good idea, and in fact I'm reluctant to do it. But is there any other way to not having to do my job literally with System Settings open all the time? Or, is there a way to make it recognize my own code as safe?

What you are describing is something completely different. See Gatekeeper and code signing | Apple Developer Forums

Finally discovered the answer. Hope this helps.

You need to disable both Gatekeeper (enable Anywhere) and SIP(System Integrity Protection).

To disable SIP:

Step 1: Enter macOS recovery mode. Depending on whether your computer is an Intel or ARM chip (M1, M2, M…), there will be different ways to enter recovery.

• ARM chip: Turn off the device completely, press and hold the power button until the screen displays the words “Loading startup options”, then release the power button.
• Intel chip: Click the Apple icon on the menu bar, select Restart, then press Command R and hold until the startup screen appears.

Step 2: Open Terminal from the menu bar above. Suppose you do not immediately see this screen when entering recovery. In that case, you may have to go through steps such as selecting Options, selecting User, and entering the password to open the device.

Step 3: Enter this command line into Terminal to disable SIP on Mac. The system may ask for a password to disable SIP; enter your device’s password and then Enter.

csrutil disable

You may be asked by the system, “Allow booting unsigned operating system and any kernel extensions for OS Macintosh HD? [y/n]” , then you need to enter “y” and then Enter to continue.

Step 4: Check the results returned by the system. If you see “Successfully disabled System Integrity Protection” or “System Integrity Protection is off” in Terminal, you have successfully disabled SIP on Mac. Now enter the reboot command and then Enter to reboot the device.