• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Code Signing for Mac application
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Code Signing for Mac application


  • Subject: Re: Code Signing for Mac application
  • From: "Paul Sanders" <email@hidden>
  • Date: Tue, 16 Feb 2010 23:04:39 -0000

I don't think so.  All files are owned by me (pauls/staff) during the build and then Package Maker does whatever it does at the end.
 
Maybe it was the fact that Package Maker was relocating our install without us being aware of it.  This is an unwelcome behavioural change on Snow Leopard and that seemed to be where the problems arose.  It means that if a user has dragged the original installation of the app to a different folder, we would fail to clear out the Resources folder before installing a new version (because it is not where we expect to find it), and that in turn would cause trouble if we removed a file in version B that had been present in version A.  But I'm sure this all happened before we ever released version B.  But then again, I cannot reproduce the problem here.  It's all very vexing.
 
Our error message was particularly alarming ("This program has been tampered with") and the app refused to run.  I think that's why users got in touch.  I have to admit that we didn't gather a lot of data because we needed to fix the problem PDQ.  Apps that won't install or crash on startup are not exactly popular!
 
Paul Sanders.
 
----- Original Message -----
From: "Alastair Houghton" <email@hidden>
To: "Graham Lee" <email@hidden>
Cc: "Paul Sanders" <email@hidden>; "Xcode Users" <email@hidden>
Sent: Tuesday, February 16, 2010 10:41 PM
Subject: Re: Code Signing for Mac application

I don't recognise that problem.  If it did happen, we'd be getting lots of complaints, because our software displays an alert if it isn't signed properly (we do that so we don't accidentally ship un-signed code), and we've been code signing our apps for some time now.

My guess is that Paul's app has some file with special permissions in its Resources folder that is preventing Finder from copying it properly.

Kind regards,

Alastair.

--
http://alastairs-place.net

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Code Signing for Mac application (From: Gabriele de Simone <email@hidden>)
 >Re: Code Signing for Mac application (From: "Paul Sanders" <email@hidden>)
 >Re: Code Signing for Mac application (From: Graham Lee <email@hidden>)
 >Re: Code Signing for Mac application (From: Alastair Houghton <email@hidden>)

  • Prev by Date: Re: Code Signing for Mac application
  • Next by Date: Re: Code Signing for Mac application
  • Previous by thread: Re: Code Signing for Mac application
  • Next by thread: Re: Code Signing for Mac application
  • Index(es):
    • Date
    • Thread