Opened 6 years ago
Closed 22 months ago
#4829 closed defect (fixed)
Windows installers fail SmartScreen checks
Reported by: | casella | Owned by: | adeas31 |
---|---|---|---|
Priority: | blocker | Milestone: | 1.20.0 |
Component: | Installation program | Version: | |
Keywords: | Cc: |
Description
When installing OMC on Windows, the SmartScreen filter identifies the OMC installer as suspicious software from unidentified authors, and requires to give explicit consent to perform a potentially dangerous installation.
This may be ok for hardened hackers that know about the OSMC, but it's not projecting an image of quality and dependability on the sofware, particularly for industrial and corporate use. Looking like potential malware is not a very good marketing strategy :)
I would recommend that from 1.13.0 we start signing the installer with a certificate, so that we avoid this kind of problems. More information on how to do this is found here
Change History (8)
comment:1 Changed 6 years ago by sjoelund.se
comment:2 Changed 5 years ago by casella
- Milestone changed from 1.13.0 to 1.14.0
Rescheduled to 1.14.0
comment:3 Changed 5 years ago by casella
- Milestone changed from 1.14.0 to 2.0.0
comment:4 Changed 5 years ago by adeas31
comment:5 Changed 5 years ago by adrpo
@adeas31, I think we can self sign the installer for now until we buy one of these. We need some bureaucracy for this (and therefore Peter), we had it before for the openmodelica.org server from StartSSL which is now gone.
comment:6 Changed 4 years ago by AnHeuermann
Having this for version 1.16.0 would be great.
In my opinion publishing a version for Windows that is blocked by SmartScreen leaves no good impression for first-time users.
@casella How important is this in your opinion? Do you want to leave it for 2.0.0?
comment:7 Changed 2 years ago by casella
Let's continue the discussion on the GitHub ticket #4829
comment:8 Changed 22 months ago by casella
- Milestone changed from 2.0.0 to 1.20.0
- Resolution set to fixed
- Status changed from new to closed
Fixed for all versions, which are now signed with an appropriate certificate.
We have signed the Linux installers for a long time. Yes, we should do it for Windows as well...