- Getting Started
- Install wyBuild
- Video Tutorial
- Step-by-step walkthrough
- New release workflow
- Basics
- FAQ (Frequently asked questions)
- Executing files
- Registry changes
- Distribute wyUpdate
- Translate wyUpdate
- Silently Check for Updates
- Silently update Windows Services
- Requirements
- Automatic Updater
- AutomaticUpdater intro
- Tutorial for Windows Forms apps
- Tutorial for WPF apps
- Tutorial for Windows Services
- AutomaticUpdater Members
- Translate the AutomaticUpdater
- About
- Changes in 2.6.18
- Advanced
- Build from Commandline
- Encrypting updates
- Commands and Variables
- COM dll registering / unregistering
- Custom wyUpdate Version
- Download sites
- Limit or prevent updates
- Offline updates
- Override the Server Site
- Proxies in wyUpdate
- Services (start / stop)
- Signing Updates in wyBuild
- Version Numbers
- wyUpdate Commandline
Signing Updates in wyBuild
wyBuild comes with the ability to sign your updates. What this means is that only updates signed by you can be installed to your end-users.
How update signing works
The first time you save your wyBuild project a 2048-bit RSA Public/Private key is generated. The private key is used to sign your updates after they are built. The public key is included in "client.wyc" and is used to validate updates. If an update fails to validate, then wyUpdate rejects the update.
Changing the signing keys
The first time you save a project your update signing keys are generated automatically. However you can change these keys or generate new signing key by click File->Properties and going to the "Signing" tab.
Click "Generate New Keys" or copy and paste another key from another project.