Gatekeeper 10.9.5 being a tight-arse? Yep…
This issue won’t affect most people, but it has affected some. If you have applications you run that are codesigned (code signed) on a computer running a version of OS X earlier than 10.9.x you may find they no longer open.
This article on TAUW explains the issue in detail.
The standard work around is to go into the Gatekeeper settings and set it to allow opening of applications downloaded from anywhere. If you use that method, you may want to set it back to one of the other two options if you’re concerned about you or someone else (children, for instance) running apps not approved by Apple on your computer.
Another option is to right-click (two-finger click) the application, and click “Open” in the context menu. Here’s a random example of what that menu looks like, when right-clicking or two-finger clicking on an application:
But apparently there are cases when this may not work. I’ve seen, for instance, numerous reports of people receiving a message such as, “This patch seems to be corrupted. Please make sure you get your patchers from a trusted source. If you believe you did, try uncompressing it with Mac OS X’s Archive Utility.”
I can’t say it’s a message the makes much sense to me. What is a “patcher” and what has the Mac OS X Archive Utility got to do with it? Well, whatever the case, here’s a possible solution:
Fixing the “This patch seems to be corrupted” issue
The following link will give you a 10.9.4 version of the Codesign file that was replaced in 10.9.5.
Download this file, and make the following changes to your system.
1) Go to the /usr/bin/ folder (you’ll need to make sure Show Hidden items is activated in Finder’s View menu (if you don’t have that option, look up online how to turn on hidden files, or install XtraFinder). Or just use the Go menu in Finder, then Go to folder, and past in /usr/bin/
2) Locate the file called codesign
3) Rename it to codesign.1094 (just tack .1094 on the end of the file name)
You will need to enter you system password (the one you use to log into your computer with). You will need to do this at various stages in this process, so just go ahead a enter it each time.
4) Drag or copy/paste the downloaded codesign file into the /usr/bin/ folder.
The end result will look something like this: (ignore the codesign.je file—that was me testing another solution to this issue)
You should now be able to open your troublesome apps and patchers.
For the average Apple user, I don’t recommend leaving this 10.9.4 codesign file in place. Use it for what you need to get done, and then rename it to something like codesign.1094 and then take the 1095 off the original file you named codesign.1095 at the beginning of this process. Basically, put things back to how they were. There’s no problem leaving a copy of the codesign.1094 file in that /bin folder, in case you need it again.
Of course, if you feel comfortable foregoing Apple’s pre-cautious code-signing changes, then leave the 10.9.4 file there if that suits you better. I see no reason to though.
UPDATE: Translating a page I found in German, I gather the “patchers” referred to by the above-mentioned error message are “Special K” software patchers (to get around registration requirements, etc.). I can’t tell if there are legal “patchers” but since the OS X generated error message refers to “patchers” I can only assume there must be.