Re: Code signing fails due to timestamp
Re: Code signing fails due to timestamp
- Subject: Re: Code signing fails due to timestamp
- From: Wim Lewis <email@hidden>
- Date: Tue, 20 Nov 2012 16:31:16 -0800
On 20 Nov 2012, at 2:41 PM, Todd Heberlein wrote:
> But I get the error:
>
> Code signing operation failed
> The timestamp service is not available. Make sure your network connection is online
>
> I am online. Does anyone know what might be causing this? If the NTP server I am using is down, how can I check that? (how can I check what NTP server my Mac uses?)
I don't think that NTP is what it's using here. Even if you're signing with your own certificate, the code signature includes a signed timestamp, signed by an Apple certificate. Presumably codesign needs to contact Apple's servers to send them a sha-1 hash and receive back a signed timestamp of that hash.
(Probably it does so by an HTTP request to timestamp.apple.com --- just guessing, from the contents of Security.framework/Versions/A/Resources/TimeStampingPrefs.plist.)
_______________________________________________
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