See http://public.kitware.com/Bug/view.php?id=13532

Considering that certificate has been ordered and should be available in the coming two business days.

I re-targeted the issue.

I had understood that Kitware was planning to sign the packages.

Did the certificate idea not work out as planned? I see that the associated cmake issue is still open.

It would be great if this could be solved for release 4.3.

Looking back at email from March 22, my understanding was that Kevin was planning to work on this.

// ----------------------------------------------------------
From: Ron - Fri, Mar 22, 2013 at 9:54 AM

FYI. No action needed as far as I understand it.

-------- Original Message --------
Subject: slicer.org code signing certificates
Date: Fri, 22 Mar 2013 09:26:22 -0400
From: Michael Halle <mhalle@bwh.harvard.edu>
To: pieper@bwh.harvard.edu, "Kikinis@bwh.harvard.edu" <Kikinis@bwh.harvard.edu>
CC: KKAMMER@PARTNERS.ORG

Steve, Ron,

Kevin from Partners is in the process of getting the wildcard SSL
certificates for slicer.org. We will do the certificate stuff before we
consolidate registrars, since there doesn't seem to be a
Partners-favored registrar.

As a bonus, Kevin is working to get slicer.org a code signing
certificate. That means we create valid apps for the Mac and other
platforms.

Steve, if you see communication from your registrar about slicer.org or
na-mic.org, please either respond affirmatively or forward the email to
me and Kevin, who is CC'ed here.

Thanks.
--Mike

I will send a followup question to Mike and Kevin to see if the certificates are available.

macOS stable 4.10 release is now signed. And instructions to sign future release have been added:

https://www.slicer.org/wiki/Documentation/Nightly/Developers/ReleaseProcess#Manually_sign_packages

https://www.slicer.org/wiki/Documentation/Nightly/Developers/ReleaseProcess#macOS_Code_Signing