Installers, Updates and Code Signing for Desktop Software

Getting software onto a customer machine and keeping it current is a feature in its own right. Operating systems treat unsigned code with suspicion: Windows SmartScreen warns about unrecognised downloads, and macOS Gatekeeper will not open downloaded applications unless they are signed with a Developer ID and notarised by Apple. Add installers, permissions and an update mechanism, and release engineering becomes a significant piece of work that is best automated from the start.

At a glance

Authenticode
The Windows code-signing format for executables, libraries, drivers and installers.
Notarised
macOS software distributed outside the App Store is checked by Apple and given a ticket.
Timestamp
A trusted timestamp keeps a signature valid after the signing certificate expires.
HSM
Publicly trusted code-signing keys must be held in hardware or a cloud signing service.

The problem

Signing left to the week before release causes delays. Certificates need identity validation by the issuing authority, keys must be held in hardware under current industry rules, and notarisation requires the hardened runtime, which can expose problems in the application itself.

Updates are the larger risk. An update channel that does not verify what it downloads lets anyone who can tamper with the server or the network install code on every customer machine.

Sign everything you ship, verify everything you install, and automate both so they happen on every build.

Platform by platform

On Windows, sign executables, DLLs and the installer with Authenticode and a timestamp, and package as MSI, MSIX or an installer built with tools such as WiX or Inno Setup. SmartScreen reputation builds over time for a publisher and its files, so expect early warnings to fade rather than vanish on day one.

On macOS, sign with a Developer ID certificate, enable the hardened runtime, submit to the notary service with notarytool and staple the ticket to the app, disk image or package. On Linux, distribute through signed repositories, Flatpak, Snap or AppImage depending on the audience.

What good looks like

Obtain signing certificates early, keep the keys in an HSM or cloud signing service, and give the build system, not individual laptops, the ability to sign.

Automate the pipeline: build, sign binaries, package, sign the installer, notarise on macOS and publish, with the same steps for every release.

Choose an update mechanism that verifies signatures before installing, supports staged rollout and can roll a bad release back.

Signing and packaging by platform
PlatformSigningExtra stepCommon packages
WindowsAuthenticode with timestampSmartScreen reputation builds over timeMSI, MSIX, EXE installer
macOSDeveloper ID certificateNotarisation and staplingApp in a DMG, or a PKG
LinuxGPG-signed packages or repositoriesStore review for Snap or FlathubDEB, RPM, Flatpak, Snap, AppImage
Requirements for software distributed outside the platform app stores.

A release pipeline

  1. Build: Clean, reproducible environment
  2. Sign binaries: Executables and libraries
  3. Package: Installer or app bundle
  4. Sign and notarise: Installer signed, macOS notarised
  5. Publish: Download page and update feed
  6. Roll out: Staged, monitored, reversible
Run on the build server for every release, never by hand.

What it changes

Trust

Customers install the software without alarming warnings or security workarounds.

Integrity

Signatures prove each file came from you and has not been altered.

Repeatability

Automated signing and packaging work the same way for every release.

Safe Updates

Verified, staged updates fix problems without creating new ones across the whole base.

Where to go next

Software that installs drivers has extra requirements. Windows kernel drivers must be signed through Microsoft, and macOS hardware access usually goes through DriverKit and system extensions.

Keep update servers and signing keys separate. An attacker who compromises the download server should still be unable to produce a valid signature.

Problems this prevents

  • Download warnings that scare customers away
  • Release delays waiting for certificates
  • Signing keys on a developer laptop
  • An update channel that installs unverified code

Discuss your project

Email support@aavico.com or use Get in Touch when the website finishes loading.