Project

Profile

Help

Actions
Send by e-mail Copy link

Bug #4233

closed

.NET Executables not code-signed

Added by O'Neil Delpratt almost 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
O'Neil Delpratt
Category:
.NET API
Sprint/Milestone:
-
Start date:
2019-06-13
Due date:
% Done:

100%

Estimated time:
Legacy ID:
Applies to branch:
9.9, trunk
Fix Committed on Branch:
9.9, trunk
Fixed in Maintenance Release:
9.9.1.5
Platforms:

Description

Reported by user:

I noticed that your installer .exe files aren’t code-signed, which means Windows Defender SmartScreen blocks them by default.

Actions
Copy link
 #1

Updated by O'Neil Delpratt almost 5 years ago

This is something we should be doing. We will investigate to add the build script the signing of exe files.

See some notes from globalsign:

https://support.globalsign.com/customer/en/portal/articles/2720229-code-signing-for-windows-7-and-8-token-based-

Actions
Copy link
 #2

Updated by O'Neil Delpratt almost 5 years ago

Status update: We did not get this issue resolved in time for the 9.9.1.4 maintenance release, but will be investigating it further shortly.

Actions
Copy link
 #3

Updated by O'Neil Delpratt almost 5 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100
  • Fix Committed on Branch 9.9, trunk added

We have now added the signing of our exe files to our build process, which will be available in the next maintenance release.

Actions
Copy link
 #4

Updated by O'Neil Delpratt over 4 years ago

  • Status changed from Resolved to Closed
  • Fixed in Maintenance Release 9.9.1.5 added

Bug fix applied in the Saxon 9.9.1.5 maintenance release.

Please register to edit this issue

Actions
Send by e-mail Copy link

Also available in: Atom PDF