logo

The ConnectWise Control forum has moved to ConnectWise University! This forum has been locked and is in read-only mode. Click here for instructions on how to access the new forum.

Welcome Guest! You can not login or register.

Notification

Icon
Error

Options
Go to last post Go to first unread
mbutler755  
#1 Posted : Tuesday, December 16, 2014 5:33:11 PM(UTC)
mbutler755


Rank: Newbie

Joined: 12/16/2014(UTC)
Posts: 9
Man
United States
Location: Peoria

I have managed to code-sign my installers to get them to avoid the smart screen filter. However, is there a way, I can automate it during the build process of an installer to automatically sign it with my code signing certificate?

Scott  
#2 Posted : Tuesday, December 16, 2014 7:01:56 PM(UTC)
Scott


Rank: Administration

Medals: Level 4: Wise Old Owl! Received 100 Thanks!

Joined: 3/28/2014(UTC)
Posts: 2,862
United States

Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
Which file did you code-sign? Was it an Access client installer that you downloaded from the Host page?

Ideally you would add your signature to the stub file in the Bin directory (C:\Program Files (x86)\ScreenConnect\Bin). That is a parameter-less file that ScreenConnect populates when you download an installer from the Host page. Code-signing that file ensures that all built client installers have your certificate.
ScreenConnect Team
mbutler755  
#3 Posted : Tuesday, December 16, 2014 7:25:01 PM(UTC)
mbutler755


Rank: Newbie

Joined: 12/16/2014(UTC)
Posts: 9
Man
United States
Location: Peoria

Originally Posted by: Scott Go to Quoted Post
Which file did you code-sign? Was it an Access client installer that you downloaded from the Host page?

Ideally you would add your signature to the stub file in the Bin directory (C:\Program Files (x86)\ScreenConnect\Bin). That is a parameter-less file that ScreenConnect populates when you download an installer from the Host page. Code-signing that file ensures that all built client installers have your certificate.


Yes, I signed the access client installers to avoid the smart screen filter. Can you tell me which files I should sign from the list below?

Elsinore.ScreenConnect.Client.apk
Elsinore.ScreenConnect.Client.application
Elsinore.ScreenConnect.Client.dll
Elsinore.ScreenConnect.Client.exe
Elsinore.ScreenConnect.Client.exe.jar
Elsinore.ScreenConnect.Client.jar
Elsinore.ScreenConnect.Client.manifest
Elsinore.ScreenConnect.Client.zip
Elsinore.ScreenConnect.ClientBootstrap.exe
Elsinore.ScreenConnect.ClientBootstrap.jar
Elsinore.ScreenConnect.ClientService.exe
Elsinore.ScreenConnect.ClientService.exe.config
Elsinore.ScreenConnect.ClientSetup.exe
Elsinore.ScreenConnect.ClientSetup.msi
Elsinore.ScreenConnect.Core.dll
Elsinore.ScreenConnect.Core.jar
Elsinore.ScreenConnect.Relay.dll
Elsinore.ScreenConnect.Server.dll
Elsinore.ScreenConnect.Service.exe
Elsinore.ScreenConnect.Service.exe.config
Elsinore.ScreenConnect.Web.dll
Elsinore.ScreenConnect.Windows.dll
Elsinore.ScreenConnect.WindowsClient.exe
Elsinore.ScreenConnect.WindowsClient.exe.config
Elsinore.ScreenConnect.WindowsServer.dll

I was thinking the EXEs and MSIs should take care of the issue. Am I correct in assuming that?
Jake  
#4 Posted : Tuesday, December 16, 2014 9:18:50 PM(UTC)
Jake


Rank: Administration

Medals: Level 4: Wise Old Owl! Received 100 Thanks!

Joined: 4/9/2010(UTC)
Posts: 2,061

Thanks: 1 times
Was thanked: 393 time(s) in 188 post(s)
In 5.1 we code sign all exes, including the installer.

Code signing the msi won't do any good, because it is modified at runtime.
ScreenConnect Team
mbutler755  
#5 Posted : Wednesday, December 17, 2014 5:02:23 PM(UTC)
mbutler755


Rank: Newbie

Joined: 12/16/2014(UTC)
Posts: 9
Man
United States
Location: Peoria

Originally Posted by: Jake Go to Quoted Post
In 5.1 we code sign all exes, including the installer.

Code signing the msi won't do any good, because it is modified at runtime.


...but I could sign the EXEs since they won't be modified? What's the timeline for 5.1s release?
Alexander  
#6 Posted : Monday, December 22, 2014 4:46:44 PM(UTC)
Alexander


Rank: Administration

Medals: Level 3: Shirt off your back! Received 25 Thanks!

Joined: 7/23/2013(UTC)
Posts: 715
Man
Location: Raleigh, NC

Was thanked: 66 time(s) in 63 post(s)
Yes, you can sign the exes. For 5.1, we're looking at maybe a couple weeks, though that's certainly not set in stone. In the meantime, you can keep up with prereleases on the release log if you're interested.
ScreenConnect Team
mbutler755  
#7 Posted : Tuesday, December 23, 2014 7:46:09 PM(UTC)
mbutler755


Rank: Newbie

Joined: 12/16/2014(UTC)
Posts: 9
Man
United States
Location: Peoria

Thank you for your input. I have signed all EXEs for now with my code signing certificate. I look forward to the 5.1 release when you sign them with your code cert. Hopefully, the MSI will be signable also because that would probably be what I want to distribute to most folks. It's especially useful for GPO installations.
RdWing  
#8 Posted : Friday, November 11, 2016 10:24:58 PM(UTC)
RdWing


Rank: Guest

Joined: 11/11/2016(UTC)
Posts: 5
United States
Location: SF Bay Area

Originally Posted by: Scott Go to Quoted Post
Which file did you code-sign? Was it an Access client installer that you downloaded from the Host page?

Ideally you would add your signature to the stub file in the Bin directory (C:\Program Files (x86)\ScreenConnect\Bin). That is a parameter-less file that ScreenConnect populates when you download an installer from the Host page. Code-signing that file ensures that all built client installers have your certificate.


Can somebody from the dev/support team elaborate on how this would be acomplished? I have a certificate I want to use to sign the installers to avoid the SmartScreen hassles. I use the self-hosted product running on Ubuntu in azure.

Alexander  
#9 Posted : Monday, November 14, 2016 6:00:20 PM(UTC)
Alexander


Rank: Administration

Medals: Level 3: Shirt off your back! Received 25 Thanks!

Joined: 7/23/2013(UTC)
Posts: 715
Man
Location: Raleigh, NC

Was thanked: 66 time(s) in 63 post(s)
This thread has more details (and it looks like you found it already, so this is mostly for anyone else coming across this thread rather than the other one).
ScreenConnect Team
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.