Re: No access to Apple's timespam service
Re: No access to Apple's timespam service
- Subject: Re: No access to Apple's timespam service
- From: Wim Lewis <email@hidden>
- Date: Mon, 15 Apr 2013 11:32:31 -0700
On 13 Apr 2013, at 8:38 AM, Filhol Alain wrote: When preparing the Archive, xCode gives me the error message Code signing failed The timestamp service is not available. Make sure your network connection is online.
The Code Signing process is successful if I bypass our proxy/firewall. However this is not an option since I have to carry my iMac 27" over about 500m each time I want to sign an application !!!
Is it possible to replace the default timestamp service used by xCode by another one ?
The codesign command, at least on 10.8, takes a "--timestamp [servername]" flag to specify a non-Apple time stamping server, and you can specify custom codesign flags in Xcode. You can also set it to "none" so that the build will not be cryptographically timestamped at all. I don't know if there's any reason not to set it to "none" --- I haven't tried it, but I've wondered if it might not be a good idea on our continuous integration servers etc. Or even for all of our builds. Has anyone experimented with this?
This is also a handy option to know about for when Apple's servers are offline :)
(Note that this isn't the same as NTP or other clock synchronization protocols — the codesign program is sending something, probably a hash of the app, to Apple's server via HTTP and getting a signed timestamp of that hash back.)
|
_______________________________________________
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