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

[Markus Mützel]

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

Fwiw, attached are the dialogues that display when executing the unsigned
Windows installer (albeit on a German locale).
The text translates approximately to:
> The computer was protected by Windows
> The Windows Defender SmartScreen prevented the start of an unknown app. The
execution of the app might represent a risk to the PC.
> More information
> "Don't execute"

And in the second window:
> App: octave-5.2.0-w64-installer.exe
> Author: Unknown Author
> "Execute anyway"  "Don't execute"

An unwary user would probably not realize that they need to click on the
underlined text (More information) in the first window to get the option to
execute the installer anyway in the second window.


This resource [1] suggests that even a self-signed executable can gain trust
over time. I don't know if this is true.
It also gives step-by-step instructions on how to sign a Windows executable
with Linux tools.
Maybe we should give it a try?

[1]: https://reiners.io/signing-windows-applications-from-linux/

(file #48352, file #48353)
    _______________________________________________________

Additional Item Attachment:

File name: installer_not_signed_1.png     Size:24 KB
    <https://savannah.gnu.org/file/installer_not_signed_1.png?file_id=48352>

File name: installer_not_signed_2.png     Size:36 KB
    <https://savannah.gnu.org/file/installer_not_signed_2.png?file_id=48353>



    _______________________________________________________

Reply to this item at:

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

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