Re: Annual codesign pain point

Well, I guess that didn't come through. I was wondering if you still get that certificate mismatch now that the image is corrected. Sent from my iPhone > On Jun 19, 2017, at 8:29 AM, Alex Zavatone wrote: > > > ___ > > Cocoa-dev mailing list (Coco

Re: Annual codesign pain point

___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.co

Re: Annual codesign pain point

On 19 Jun 2017, at 3:12 pm, Graham Cox wrote: > > Not sure why this wasn’t picked up in my previous builds though, since I was > compiling on 10.11. The change was made in 10.12. -- Shane Stanley , ___ Cocoa-dev mailing list (Cocoa-dev@lists.ap

Re: Annual codesign pain point

Bingo! I had one image resource with a resource fork. Not sure why this wasn’t picked up in my previous builds though, since I was compiling on 10.11. But that does seem to have been the issue. Thanks to Alex for his unending patience offline sifting through all the signing certificate issues,

Re: Annual codesign pain point

On 19 Jun 2017, at 1:06 pm, Graham Cox wrote: > > resource fork, Finder information, or similar detritus not allowed See: -- Shane Stanley , ___ Cocoa-dev mailing list (Cocoa-de

Re: Annual codesign pain point

I dunno, but I two things jump out at me: On Jun 18, 2017, at 20:06 , Graham Cox wrote: > > 2017-06-19 02:52:16 + Disqualifying 0x7ff548966ae0; name='3rd Party Mac Developer Installer: REDACTED, LLC > (V55NQN)’, […] This is a Mac App Store certificate. If it’s “disqualifying” it only

Re: Annual codesign pain point

the logs to me > in the Finder. > > It’s unclear what the reason for the codesign failure is. The verbose log > ends with: > > 2017-06-19 02:52:16 + Disqualifying 0x7ff548966ae0; name='3rd Party Mac Developer Installer: REDACTED, LLC > (V55N

Annual codesign pain point

. Rather than a helpful error message, it just offers to reveal the logs to me in the Finder. It’s unclear what the reason for the codesign failure is. The verbose log ends with: 2017-06-19 02:52:16 + Disqualifying due to certificateKind (input 1.2.840.113635.100.6.1.13 doesn't

Re: Codesign assumes folder structure, fails.

> On Jul 25, 2016, at 6:15 PM, Graham Cox wrote: > > Hi all, > > I’m getting an error from codesign when it tries to sign a third-party > embedded framework. > > The error is: > > /Users/grahamcox/Library/Developer/Xcode/DerivedData/Drawkit-hlbdxcwqkoiqzlesbkf

Codesign assumes folder structure, fails.

Hi all, I’m getting an error from codesign when it tries to sign a third-party embedded framework. The error is: /Users/grahamcox/Library/Developer/Xcode/DerivedData/Drawkit-hlbdxcwqkoiqzlesbkfsrobctzke/Build/Products/Debug/Ortelius 2.app/Contents/Frameworks/GEOS.framework/Versions/A: No such

Re: Codesign broken in 10.11.4

> On Apr 7, 2016, at 9:25 AM, Trygve Inda wrote: > >> This may be relevant, though it does talk about issues with pref panes as >> well. >> >> http://mjtsai.com/blog/2016/03/31/gatekeeper-bug-in-mac-os-x-10-11-4/ > > Yup. That sums it up. > > The short story: tested with a default Xcode comma

Re: Codesign broken in 10.11.4

Could this be relevant to the changes in Xcode for iOS library development where you have to us archive instead of build to get the correct architectures in your bundle? > On Apr 7, 2016, at 12:25 PM, Trygve Inda wrote: > >> This may be relevant, though it does talk about issues with pref pane

Re: Codesign broken in 10.11.4

> This may be relevant, though it does talk about issues with pref panes as > well. > > http://mjtsai.com/blog/2016/03/31/gatekeeper-bug-in-mac-os-x-10-11-4/ Yup. That sums it up. The short story: tested with a default Xcode command line tool that says "Hello World". 1) Build a command line to

Re: Codesign broken in 10.11.4

t; everything is signed from the inside-out. > > In terminal (on two different machines running 10.11.3) I get: > > spctl -a -t exec -vv My.prefPane > > /Volumes/Path/To//My.prefPane: accepted > source=Developer ID > origin=Developer ID Application: My Company, In

Re: Codesign broken in 10.11.4

I get: > > spctl -a -t exec -vv My.prefPane > >/Volumes/Path/To//My.prefPane: accepted >source=Developer ID >origin=Developer ID Application: My Company, Inc. > > codesign --verbose=4 --deep --strict My.prefPane > >/Volumes/Path/To//My.prefPane: valid on di

Codesign broken in 10.11.4

n: My Company, Inc. codesign --verbose=4 --deep --strict My.prefPane /Volumes/Path/To//My.prefPane: valid on disk /Volumes/Path/To//My.prefPane: satisfies its Designated Requirement In terminal (on two different machines running 10.11.4) I get: spctl -a -t exec -vv My.prefPane /Vo

Re: codesign v2 problem on 10.8.5 and earlier

Hi, it seems the issue is related to a 3rd party framework I am using. Tamas > On 24 Nov 2014, at 08:32, Tamas Nagy wrote: > > Hi, > > switched to codesign v2 to match the new requirements on 10.9.5 and 10.10. > The sign works well on 10.9.5 and later, but on 10.8.

codesign v2 problem on 10.8.5 and earlier

Hi, switched to codesign v2 to match the new requirements on 10.9.5 and 10.10. The sign works well on 10.9.5 and later, but on 10.8.5 (with the latest security update installed) the verify process (codesign —verify —deep —verbose=2 …) reports “bundle format unrecognized, invalid or unsuitable

Re: How to get Mac codesign certificate?

> > The SMJobBless example code has a ReadMe.txt file that explains how to make a > self-signed certificate, and how to set up the project to use it. It worked > correctly when I tried it. > > https://developer.apple.com/library/mac/#samplecode/SMJobBless/Listings/ReadMe_txt.html I got it wor

Re: How to get Mac codesign certificate?

The SMJobBless example code has a ReadMe.txt file that explains how to make a self-signed certificate, and how to set up the project to use it. It worked correctly when I tried it. https://developer.apple.com/library/mac/#samplecode/SMJobBless/Listings/ReadMe_txt.html > You can get a self-sign

Re: How to get Mac codesign certificate?

On Mar 17, 2012, at 9:54 AM, Marco Tabini wrote: > 'm not an expert, but I think the free cert they provide cannot be used for > code signing. It can’t. Only Apple’s certs will work with Gatekeeper. > One other alternative may be the Developer ID initiative that Apple has > announced as part o

Re: How to get Mac codesign certificate?

On Mar 17, 2012, at 11:14 AM, Gerriet M. Denkmann wrote: > The problem: The documentation about SMJobBless says: "The calling > application and target executable tool must both be signed." > > So it seems that new technologies require code signing. Makes sense. But: > where and how do I get a

Re: How to get Mac codesign certificate?

> > So it seems that new technologies require code signing. Makes sense. But: > where and how do I get a free certificate? > Not sure you can yet. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moder

Re: How to get Mac codesign certificate?

On 17 Mar 2012, at 22:41, Roland King wrote: > >> One other alternative may be the Developer ID initiative that Apple has >> announced as part of OS X 10.8 Mountain Lion, but I can't figure out if >> that's still under NDA and don't want to incur the wrath of the mods :-) > I assumed thats wh

Re: How to get Mac codesign certificate?

> One other alternative may be the Developer ID initiative that Apple has > announced as part of OS X 10.8 Mountain Lion, but I can't figure out if > that's still under NDA and don't want to incur the wrath of the mods :-) > > I assumed thats what the original poster was referring to. I'm als

Re: How to get Mac codesign certificate?

On 17/03/2012, at 7:54 AM, Marco Tabini wrote: >> Can you not just use a free provider, like http://www.startssl.com/? > > I'm not an expert, but I think the free cert they provide cannot be used for > code signing. FWIW they can; they'd be pretty useless otherwise. Many of them are marked, ho

Re: How to get Mac codesign certificate?

> Can you not just use a free provider, like http://www.startssl.com/? I'm not an expert, but I think the free cert they provide cannot be used for code signing. One other alternative may be the Developer ID initiative that Apple has announced as part of OS X 10.8 Mountain Lion, but I can't fig

Re: How to get Mac codesign certificate?

>> But I want to codesign my OS X apps. >> So how do I get the necessary certificate? > > You need to buy it from a certificate authority, like Thawte or Verisign (or > one of the myriad resellers) and they will all be happy to sell you one at > prices that range from a

Re: How to get Mac codesign certificate?

On 2012-03-17, at 9:18 AM, Gerriet M. Denkmann wrote: > But I want to codesign my OS X apps. > So how do I get the necessary certificate? You need to buy it from a certificate authority, like Thawte or Verisign (or one of the myriad resellers) and they will all be happy to sell you

How to get Mac codesign certificate?

I am a registered developer. And I paid 80€ to get the permission to mess around with my iPhone for one year. I am NOT interested in the Mac app Store, and I do NOT want to pay another 80€. But I want to codesign my OS X apps. So how do I get the necessary certificate? Kind regards, Gerriet

Re: Codesign non-AppStore build with AppStore signing identity

e says that simply signing it will fix this. > > Can we just sign it the same way we do the version built for the App Store, > using the same digital signature? Passing an App Store certificate as an argument to the codesign tool seems to work over here. Perhaps an Apple employee will ch

Codesign non-AppStore build with AppStore signing identity

One of our apps (distributed via our website) is not signed. It seems that Parental Controls signs our app behind our back to do what it does. This obviously alters our app and breaks some integrity checks. A Tech Note says that simply signing it will fix this. Can we just sign it the same way w

codesign

hi, i'm not using xcode but want to codesign my Mac App manually. which commands do I need to enable my Mac App to connect with the APNS. regards, jaap ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin reques

Re: Codesign failure

Hi, I did redownload and reinstall the certificates. I get now: /Volumes/Spare/GraphicConverter.app: CSSMERR_TP_NOT_TRUSTED Not much better. Thorsten > Did you just download them in the last day or has it been a week or two? You > do have Xcode 3.2.5 right? For the first week or so after 3

Re: Codesign failure

account. > > Thorsten > >> Von: "Rick C." >> Datum: Sat, 20 Nov 2010 14:42:08 +0800 >> An: Cocoa Developers >> Betreff: Re: Codesign failure >> >> Also try looking on the Developer forums this was a big issue at first. I >&g

Re: Codesign failure

Hi, I did download the certificates from the section of the member site of the developer account. Thorsten > Von: "Rick C." > Datum: Sat, 20 Nov 2010 14:42:08 +0800 > An: Cocoa Developers > Betreff: Re: Codesign failure > > Also try looking on the Developer fo

Re: Codesign failure

I get as reply from: > /usr/bin/codesign -f -s "3rd Party Mac Developer Application: Thorsten > Lemke" /volumes/Master/GC7/build/Release/GraphicConverter.app > > /volumes/Master/GC7/build/Release/GraphicConverter.app: Unknown format in > import. > > Does anyone have an

Re: Codesign failure

On 19 Nov 2010, at 14:04, Thorsten Lemke wrote: > Hello, > > I try to sign my app for the Mac App Store. > > But I get as reply from: > /usr/bin/codesign -f -s "3rd Party Mac Developer Application: Thorsten > Lemke" /volumes/Master/GC7/build/Release/GraphicCon

Codesign failure

Hello, I try to sign my app for the Mac App Store. But I get as reply from: /usr/bin/codesign -f -s "3rd Party Mac Developer Application: Thorsten Lemke" /volumes/Master/GC7/build/Release/GraphicConverter.app /volumes/Master/GC7/build/Release/GraphicConverter.app: Unknown format

Re: Codesign additional items within an app bundle

On 2010 Oct 17, at 07:53, Michael Diehr wrote: > Taking my first stab at codesigning an OS X App, and I'm noticing that only > some items within the app bundle get signed Didn't read all of your message, but looks like you probably need the same answer I got last year… http://lists.apple.com/

Codesign additional items within an app bundle

Taking my first stab at codesigning an OS X App, and I'm noticing that only some items within the app bundle get signed, e.g.: codesign -s 'My Company' /path/to/my/MyApp.app seems to only sign some of the files in a bundle: MyApp.app/ Contents/MacOS/MyApp (the executa

Re: Codesign from Buid Server

signing step; either that, or if you want anyone to be able to do it, it means you can stick the password in a script without worrying too much (obviously set the permissions on the script according to your requirements). Then you need to do security unlock-keychain followed by code

Codesign from Buid Server

Hi, We have a TeamCity build server setup to produce automatic builds for our cocoa application. We also code sign our apps but this part has to be done on a dev box as the build agent (OS X 10.5) doesn¹t recognize the certificate in the system keychain (there is no login keychain when the build a