More on Digital Signatures

Jeffrey Altman wrote:
> Something else that I experimented with for these builds is code 
> signing.  Every .exe, .dll, and .cpl file in the release has been
> digitally signed with a certificate issued by MIT to [email protected].
> In addition, the NSIS and the MSI installers have also be signed.

The certificate which needs to be imported into Windows to allow the
digitally signed files to be recognized is:

    http://web.mit.edu/~jaltman/Public/OpenAFS/MITClientCA.crt
    /afs/athena.mit.edu/user/j/a/jaltman/Public/OpenAFS/MITClientCA.crt
    \\AFS\athena.mit.edu\user\j\a\jaltman\Public\OpenAFS\MITClientCA.crt

To install:

  * Execute the file and it will bring up a Certificate Properties
    dialog.  It should read "Issued To" and "Issued By" Client CA v1.

  * Press the "Install Certificate" button to start the "Certificate
    Import Wizard".

  * Press Next.

  * On the "Certificate Store" page select "Place all certificates in the
    following store"

  * Browse and select either "Trusted Root Certification Authorities" or
    "Trusted Publishers".

  * Press Next.

  * Press Finish.

All of the installers and the individual binaries can now be browsed in 
the explorer.  Right click and select Properties.  There is now a 
Digital Signatures page which will indicate that the file was signed by
[email protected].

Jeffrey Altman