Community
MSI Publisher Configurations
Deyan G,
User (Posts: 1)
Nov 16, 2015 12:42:02 pm EST
Support level: Free or trial
After configuring the MSI package to be a One-Click installation it comes up as Unknown Publisher and Windows is showing a warning message. How can we fix that in order to eliminate the warning message.
![](/upload/forum/avatar/6da/2020_11_06_0000.png)
Conrad Sallian,
Support (Posts: 2987)
Nov 16, 2015 1:58:19 pm EST
Hello Deyan,
Since we received the same through the tickets, I've responded in the tickets to avoid duplication.
Thanks.
Since we received the same through the tickets, I've responded in the tickets to avoid duplication.
Thanks.
iampedro,
User (Posts: 38)
Jan 07, 2016 11:59:55 pm EST
Conrad,
Could you also respond here for me also, please.
Could you also respond here for me also, please.
![](/upload/forum/avatar/6da/2020_11_06_0000.png)
Conrad Sallian,
Support (Posts: 2987)
Jan 08, 2016 7:57:38 am EST
To all of you guys - we found a way how to add a digital signature to custom configured installers without "going online" with our MSI configurator. So we'll soon implement this feature and any installer, including custom ones, will be signed with our digital signature.
LDM,
User (Posts: 1)
Jan 29, 2016 12:36:47 pm EST
Support level: Free or trial
Just a heads-up/FYI:
[broken link removed]
Any code signed after Jan 1, 2016 signed with a SHA-1 hash will get these warnings in IE and possibly other browsers soon if not already. It needs to be signed with SHA-2.
Effective January 1, 2016, Windows (version 7 and higher) and Windows Server will no longer trust new code that is signed with a SHA-1 code signing certificate for Mark-of-the-Web related scenarios (e.g. files containing a digital signature) and that has been time-stamped with a value greater than January 1, 2016. This cut-off date applies to the code-signing certificate itself.
This restriction will not apply to the time-stamp certificate used to time-stamp the code-signing certificate or the certificate’s signature hash (thumbprint) until January 1, 2017. After this time, Windows will treat any code with a SHA-1 time-stamp or SHA-1 signature hash (thumbprint) as if the code did not have a time-stamp signature.
[broken link removed]
Any code signed after Jan 1, 2016 signed with a SHA-1 hash will get these warnings in IE and possibly other browsers soon if not already. It needs to be signed with SHA-2.
Effective January 1, 2016, Windows (version 7 and higher) and Windows Server will no longer trust new code that is signed with a SHA-1 code signing certificate for Mark-of-the-Web related scenarios (e.g. files containing a digital signature) and that has been time-stamped with a value greater than January 1, 2016. This cut-off date applies to the code-signing certificate itself.
This restriction will not apply to the time-stamp certificate used to time-stamp the code-signing certificate or the certificate’s signature hash (thumbprint) until January 1, 2017. After this time, Windows will treat any code with a SHA-1 time-stamp or SHA-1 signature hash (thumbprint) as if the code did not have a time-stamp signature.
![](/upload/forum/avatar/6da/2020_11_06_0000.png)
Conrad Sallian,
Support (Posts: 2987)
Jan 29, 2016 12:52:00 pm EST
Hello,
Yes, thank you. We'll take that into consideration.
Yes, thank you. We'll take that into consideration.
* Website time zone: America/New_York (UTC -4)