Gatekeeper gone crazy

After installing some Adobe CC updates, Java & Flash updates as well as some security & Safari updates to my 300 Macs at the school where I work, Gatekeeper has now gone crazy. Instead of preventing you from launching an app that was not installed from the App Store, Gatekeeper is now preventing everyone from opening FILES from anywhere except the internal hard drive. Files downloaded from the Internet and Intranet. Files downloaded from a school server. Files still on the server (being opened over the network). Files on external hard drives and USB flash drives. No one can open any file without the:


"FileName" is damaged and can't be opened. You should move it to the Trash.


The only solution is turning Gatekeeper off entirely from the Security & Privacy System Preferences (General tab, select "Allow applications downloaded from: Anywhere"). If this was a one-time click of the button, that would be fine. However, Gatekeeper keeps turning itself back on! I have to push out the Terminal command to all 300 Macs every day via ARD or it comes back on. These are not applications, Gatekeeper should not be preventing users from opening Photoshop files from their personal hard drives. All of the workstations were imaged from the same disk image a couple of months ago. They're all now running Mac OS X 10.8.5 (12F45) and there's a variety of iMacs and Mac Pro towers. What do I have to do to stop this from happening?


-Doug

Posted on Oct 17, 2014 10:11 AM

Reply
8 replies

Aug 12, 2017 8:40 AM in response to etresoft

While an old thread, I have this same problem with Sierra 10.4.2. Any file (jpg, pdf) gives me this error about it being damaged, even if I created it. Gatekeeper in the System Preferences turns itself on immediately if I turn it off. I can open the files just fine from within the apps. My workaround it to use the Terminal sudo spctl --master-disable and then try to remember to "enable" when I'm done. What a pain.


If anyone has a solution which works permanently (i.e., allows Gatekeeper to not call everything damaged) it would be great to share it.


Thanks,


Mace

Oct 24, 2014 8:20 AM in response to Douglas McLaughlin

I don't think it is as simple as that. It sounds like there is a signing issue with some software that your other software is linking with. When the other software launches, it tries to load the library, fails due to the code signing issue, and then you get the error. Java is one candidate. You could have another Java that is the source of the problem. It could be some other library too. But that is almost certainly what the problem is.

Oct 24, 2014 11:29 AM in response to etresoft

Here's what I need to figure out: Why is Gatekeeper flagging documents? Isn't it a service to flag potentially harmful applications? If I double-click on an Excel spreadsheet file on one of the Macs encountering this problem, I'm challenged that the file is damaged and to put it in the trash. However, I can open Excel and open the file from inside Excel, make changes and save the spreadsheet. If I quit Excel and double-click on the file from the Finder I get the exact same challenge from the Mac claiming that the file is damaged. This is not how this service is supposed to work. I'm not concerned with launching applications (which is the only process I've been able to find examples and help with). I'm not having a problem launching applications. I'm having a problem double-clicking on documents in the Finder and Gatekeeper freaking people out that their documents are damaged.


If I must leave the Security & Privacy System Preferences set to allow applications from anywhere, fine. But it randomly keeps switching back to "Mac App Store and identified developers".


-Doug

Oct 24, 2014 11:47 AM in response to Douglas McLaughlin

I don't think GateKeeper makes any differentiation between documents and executable files. It is pretty common to get a GateKeeper error when trying to double-click a document in the Finder. You just have to track down the correct application, launch it, and then double-click the file.


I don't know why it would be randomly switching back to the default setting. In Yosemite, it does that automatically after 30 days.


Unfortunately, this is the new Apple. Things like this aren't ever going to be fixed. Apple sells devices and delights users. It is your responsibility to track down and report bugs. If 20 million other people do the same, then it might get fixed. What you describe does not occur in a standard setup, so you have to figure out what is different about your setup from the standard. Perhaps even re-create your setup from scratch. If you are really running 10.8, then it would be a good time to update because that old version is no longer supported. You do the best you can and then live with the result.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Gatekeeper gone crazy

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.