[Octave-bug-tracker] [bug #57649] [MXE Octave] Sign Windows installer with trusted certificate

[Markus Mützel]

Follow-up Comment #7, bug #57649 (project octave):

The process of creating a certificate and signing the installer is very easy.
However, it doesn't make a difference: I had to pass the installer through an
FTP server for the message to actually trigger.
The installer is definitely signed, and it is possible to inspect the
signature using the file properties in the right click menu (see attached
screenshot).
However, as expected, there is a message telling something along the lines of
"The certificate chain could be successfully traversed. However, it ended at a
root certificate that isn't trusted."

The warning message that is displayed when trying to use the installer is
still the same.

There is still the possibility that even the self signed certificate could
gain trust over time. But I haven't found an "official" source confirming that
this is the case.

(file #48373)
    _______________________________________________________

Additional Item Attachment:

File name: bug57649_signature_details.png Size:14 KB
   
<https://savannah.gnu.org/file/bug57649_signature_details.png?file_id=48373>



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57649>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/