Digitally sign the installers with YOUR certifictae

Avatar
  • updated
  • Pending Review

As a software vendor you need to digitally sign the installers for your product.  Every other remote support vendor does this.  You should not be making your clients pay for their own certificates to sign your installers, they will always have issues with reputation and being blocked by endpoint security.  It is simple common sense to make a trusted installer (exe and msi), sign it yourself with your own certificate.  Do not allow clients (i mean connectwise customers) the ability to edit this installer, but do provide install options by switches to specify server, clientname, groups etc to target it.  Then provide further options by policy from the server to assign branding, hide the icon, hide the banner, etc etc.

Avatar
0
Derek Howard

This exactly. The relay server URL should be configurable as an installation switch.

I think the point of the other information being baked into the installer (the various custom values) is so persons with access to the given installer can't manually change those values, which may affect how much access they have to the resulting session within ScreenConnect. Despite this, however, we as administrators should be free to pass out the stock installer (signed by ConnectWise) as we see fit, and then manually assign the various other values within ScreenConnect. If customers want to be able to bake these values into the installer and then sign it themselves, that should be optional. But for customers who can't get a code signing certificate (or are uncomfortable with the cert's private key living on the ScreenConnect server...), a stock installer should always be an option.

As for my organization, we've literally never customized the installer. The only distinct thing about our installer is the relay URL...

Avatar
0
amccabe Team Member

The relay URL is the thing that prompted this code-signing requirement in the first place. There was a concern that bad actors could manipulate an installer/client from a legitimate source to point to their own server, and thus take advantage of the trust that user had in that source and the certificate the installer/client was signed with.

Avatar
0
Juergen Meier

Since this is only really relevant to Windows:
There is absolutely no reason to customize/modify the installation package (.msi).

All necessary custom parameters can be provided by command line switches and/or a transforms file (.mst).