timestamp codesign issue

Hi all, in order to submit my application to the notarization system, in my continuous integration tools I used to run the following command to sign my app:

codesign -s "$SIGNKEY_NAME" --timestamp --options runtime myApp.app --deep

The command was working fine in the last year and allow me to notarize the application succesfully.

Starting from the last week the same code is now throwing a timestamp error:

A timestamp was expected but was not found.

And i don't know why, since nothing relevant has been changed.

UPDATE: If i try to run the same command but with the option

--timestamp=none

everything works fine :

myApp.app: signed app bundle with Mach-O thin

I though that there are some issues with the connectivity with the timestamp server, could be?

I don't know if this can help, but if i try to ping timestamp.apple.com i have the following

PING timestamp.pki-apple.com.akadns.net (17.32.213.129): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
***

Or, if i try to traceroute it:

traceroute to timestamp.pki-apple.com.akadns.net (17.32.213.129), 64 hops max, 52 byte packets

10 93-63-100-249.ip27.fastwebnet.it (93.63.100.249) 10.178 ms
  93-63-100-109.ip27.fastwebnet.it (93.63.100.109) 10.508 ms
  93-63-100-153.ip27.fastwebnet.it (93.63.100.153) 11.030 ms
11 195.66.226.145 (195.66.226.145) 44.223 ms 36.469 ms 35.383 ms
12 195.66.226.145 (195.66.226.145) 35.978 ms 35.593 ms
  17.0.10.222 (17.0.10.222) 120.316 ms
13 17.0.10.222 (17.0.10.222) 120.074 ms
  17.0.10.226 (17.0.10.226) 120.040 ms
  17.0.15.140 (17.0.15.140) 120.761 ms
14 17.0.15.177 (17.0.15.177) 119.820 ms
  17.0.15.140 (17.0.15.140) 119.926 ms
  17.0.15.177 (17.0.15.177) 119.709 ms
15 * 17.0.15.177 (17.0.15.177) 120.352 ms 120.739 ms
16 * * 17.0.15.154 (17.0.15.154) 120.043 ms
17 17.1.0.253 (17.1.0.253) 120.142 ms * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *

Could you please help me? Thanks

Up vote post of francescoesteco Down vote post of francescoesteco
1.1k views
Posted by
francescoesteco
Reply
Add a Comment

Accepted Reply

UPDATE: was a misleading firewall configuration of the IT infrastructure that was blocking the connection with port 80.

Thanks @eskimo for allow me to understand a new way fo troubleshoot with the nc command!

Posted by
francescoesteco
Up vote reply of francescoesteco Down vote reply of francescoesteco
Post marked as solved
Add a Comment

Replies

What does the following show?

% nc -v timestamp.apple.com 80
Connection to timestamp.apple.com port 80 [tcp/http] succeeded!
^C

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Posted by
eskimo
Up vote reply of eskimo Down vote reply of eskimo
Add a Comment

Thanks @eskimo

I get this error:

nc -v timestamp.apple.com 80
nc: connectx to timestamp.apple.com port 80 (tcp) failed: Operation timed out

Note: the same error doesn't occur on a different machine on a different network

Do you think that there is strange configuration of the IT infrastructure causing the issue? Or may i fix it directly in the macOS machine that runs the command?

Posted by
francescoesteco
Up vote reply of francescoesteco Down vote reply of francescoesteco
Add a Comment

UPDATE: was a misleading firewall configuration of the IT infrastructure that was blocking the connection with port 80.

Thanks @eskimo for allow me to understand a new way fo troubleshoot with the nc command!

Posted by
francescoesteco
Up vote reply of francescoesteco Down vote reply of francescoesteco
Post marked as solved
Add a Comment