How it works
You hold a certificate that ties your identity to a key pair. When you build a release, a signing tool computes a signature over the file with your private key and attaches it. When someone opens the file, the operating system checks the signature against the certificate, and the certificate against authorities it trusts. If a byte has changed since signing, the check fails.
Microsoft’s documentation states the guarantee plainly: a digital signature attached to a file identifies the distributor and shows the contents were not changed after the signature was created. This is a digital signature with a certificate added, so it can name a publisher.
Windows and macOS
| Windows | macOS | |
|---|---|---|
| Mechanism | Authenticode, applied with SignTool | Developer ID certificate, applied with codesign |
| What gets signed | .exe, .dll, .msi, .msix, .appx, .cab, .ps1 and others |
Apps, plug-ins and installer packages |
| Who checks it | Windows, and Microsoft Defender SmartScreen | Gatekeeper |
| Extra step | No separate notarization step | Notarization for Developer ID software |
| Certificate | A code-signing certificate | Developer ID Application for apps, Developer ID Installer for packages |
As of November 2026, Microsoft’s SignTool page says that Windows SDK builds 20236 and later require the file digest option /fd and the timestamp digest option /td when signing and time stamping. SignTool can sign, verify and time stamp, so the same tool covers the whole release step.
SmartScreen checks the reputation of downloaded programs and of the certificate that signed them. Per Microsoft’s documentation, an item with no established reputation is marked as higher risk and shows the user a warning. Signing does not make that warning disappear on day one.
Example commands
On macOS, the first command signs with a Developer ID certificate, the hardened runtime and a secure timestamp. The second checks the signature the way Apple’s notarization guidance suggests.
codesign --force --timestamp --options runtime \
--sign "Developer ID Application: Example Ltd (TEAMID1234)" MyApp.app
codesign -vvv --deep --strict MyApp.app
The identity and team id above are placeholders.
Two signatures in one licensed app
A paid app can carry two unrelated signatures:
| Signature | Made by | Made with | Checked by | Proves |
|---|---|---|---|---|
| Code signature | You | Your code-signing certificate | The operating system | You published this file and it is unchanged |
| License token signature | The license service | The product’s private key | Your app | This license was valid when the server answered |
Neither replaces the other. A signed app can be run by anyone who downloads it, and a valid license token does not tell the operating system your file is trustworthy.
How Clavem handles it
Clavem does not sign your binaries and does not notarize them. It stores and delivers the files you upload, so sign (and on macOS notarize and staple) before you upload. Separately, Clavem signs license tokens with an Ed25519 key that belongs to the product. For buying and renewing certificates, see code signing certificates explained, and for packaging, installer.
Questions
Is code signing the same as a license key?
No. Code signing tells the operating system who published a file and that it is unchanged. A license key tells your app that a customer paid. They are checked by different parties for different reasons.
Do I need code signing to sell software?
You can sell unsigned software, but users will see warnings. On macOS, software distributed outside the Mac App Store should be signed with a Developer ID certificate and notarized.