Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

fhall1

macrumors 68040
Original poster
Dec 18, 2007
3,853
1,285
(Central) NY State of mind
There is a workaround for this (I did this for PDFPen Pro before the new version was released and worked fine for me - use at your own risk, don't blame me if you screw something up by not following steps properly):


1. Open Keychain Access (/Applications/Utilities/Keychain Access)
2. Select "Keychain Access > Certificate Assistant > Create a Certificate…" and create a self-signed certificate (use a name without spaces and change “Certificate type” to “Code Signing”)
3. Find your newly created cert in your list and select it, then do File > Get Info on that certificate
4. select "Code Signing > Always Trust"
5. In terminal, type "sudo codesign -s <CERTIFICATE_NAME_HERE> -f /Applications/PDFPenPro.app
(obviously change the app name if you're signing a different app - and put just the cert name - no brackets)

check “Let me override defaults” in order to enter a date a few years into the future - otherwise its default is one year.

…this should re-sign the app with your own certificate, and you're set.
 
  • Like
Reactions: Partron22

Partron22

macrumors 68030
Apr 13, 2011
2,655
808
Yes
I could stand some NY myself. It's been a while.
Thanks for the tip. Likely I'll use it.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.