Re: Both Xcode or codesign fail behind a proxy (timestamp not found)
Re: Both Xcode or codesign fail behind a proxy (timestamp not found)
- Subject: Re: Both Xcode or codesign fail behind a proxy (timestamp not found)
- From: Roland King <email@hidden>
- Date: Thu, 4 May 2017 06:47:45 +0800
|
I think it's been doing this forever. I remember us talking about
it before one weekend when the time server was down. Then I found
this thread as an example
https://lists.apple.com/archives/xcode-users/2013/Apr/msg00109.html
.. hold on .. same OP, who found that apple checked its own
timeserver way back then, and it was blocked. What happened in the
intervening years, did it start working again and stop, did you
have the firewall fixed to pass it through and someone reverted
that change?
On 04/05/2017 06:11, Jens Alfke wrote:
On May 3, 2017, at 9:33 AM, Filhol Alain < email@hidden> wrote:
This is very interesting !
Where did you find that Apple changed its code-signing
procedure to check their own NTP server ?
I didn’t, you did. :) In the first message in the
thread you said that “'codesign' superbly ignores the proxy and
tries to access Apple’s timestamp server … directly.” And since
you say this only started happening recently, I’m inferring that
Apple has changed their protocol for code signing to require
hitting their NTP server.
—Jens
_______________________________________________
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
|
_______________________________________________
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