Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-33709

Windows installers should be signed by the Jenkins project

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • packaging

      To my knowledge there's not a ticket capturing this already, so I'm filing to keep track.

      The Windows installer is signed by "Infradna, Inc", I've never even heard of them!

      Really, this should be signed by SPI, Inc or Jenkins if possible

          [JENKINS-33709] Windows installers should be signed by the Jenkins project

          Andrew Bayer added a comment -

          So!

          Windows code signing certs can only be issued to either individuals or corporate entities. Since the Jenkins project is not a corporate entity, it can't be issued a certificate. SPI is a corporate entity, but, so far as I can tell, is not willing to play that role for its projects when it comes to code signing certs. We should really try contacting LibreOffice (also at SPI) to see how they do it...

          Andrew Bayer added a comment - So! Windows code signing certs can only be issued to either individuals or corporate entities. Since the Jenkins project is not a corporate entity, it can't be issued a certificate. SPI is a corporate entity, but, so far as I can tell, is not willing to play that role for its projects when it comes to code signing certs. We should really try contacting LibreOffice (also at SPI) to see how they do it...

          Alex Earl added a comment -

          The installers have been signed for some time now.

          Alex Earl added a comment - The installers have been signed for some time now.

            Unassigned Unassigned
            rtyler R. Tyler Croy
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: