I'm curious what your results would be with the stock Terminal. Do you have the settings that others have talked about under "Security > Privacy > Developer Tools" with Terminal.app listed? If so, and the results are better with Terminal, then it'd be interesting to see if the issue is fixed when you add iTerm2 to the list of exempted apps as well.
It doesn't work when there's no network connection, wonder if it would be possible to filter out and automatically block notarization traffic, or if it's all encrypted with cert pinning to prevent this type of MITM+filter.
Dropping packets when there is an otherwise working connection could potentially make the delay even worse depending on timeout or retry strategy used by Apple code. I assume that in the fast case without network connection it checks the network status flag and doesn't try to do any network connection at all.
> Hello
> /tmp/test.sh 0.00s user 0.00s system 0% cpu 5.746 total
> Hello
> /tmp/test.sh 0.00s user 0.00s system 79% cpu 0.006 total
And even if I didn't connect to my VPN:
> Hello
> /tmp/test2.sh 0.00s user 0.00s system 0% cpu 1.936 total
> Hello
> /tmp/test2.sh 0.00s user 0.00s system 78% cpu 0.005 total
That's just ridiculous and unbearable.
Apple should provide a way to disable this notarization thing, and the user should still be able to enable SIP while disabling it.
additional information:
- macOS version: 10.15.4
- terminal: iTerm2 3.3.9
- didn't install any "security" software