could we try to do such self-signing with some default (non-trusted) signature?
While creating the self-signed certificate, worth noting that the following message is reported:
@lassoan @pieper @rkikinis @hherhold A self-signed package corresponding to the most recent nightly is now available for download at https://data.kitware.com/#item/5dddb66daf2e2eed3533ec79
Note that the signing was manually done
On Mac Catalina 10.15.1 : Both the dmg and slicer require opening with a right mouse click, but do not require going to preference/security. Workable.
I did some testing using various versions with commands like this:
time /Applications/"Slicer 2.app"/Contents/MacOS/Slicer --python-code "exit()"
All the release builds, both 4.10.2 and the nighlies and the new self-signed version from Jc complete in about 10-12 seconds. My local debug build takes about 30 seconds for the same command line, whether I self-sign it or not.
I didn’t see anything particularly informative in the log stream command.
1 Like
@jcfr I can confirm that the signed package doesn’t cause the hang. The only regression is that the installer requires a right-click to open.
1 Like