Customization of Omaha Client

Introduction

The open-source Omaha builds initially "Google Update". Google Update communicates with Google's update servers, which only support Google applications.

The main difference between code compiled from this site and Google Update is the Authenticode signature and version number, and the CLSIDs of the COM objects.

In order to use Omaha for your application or organization, you must customize the source code and prevent it from conflicting with Google Update (or other forks of Omaha) on users' computers.

Versioning

The version number stored in all outputs is set in the file omaha\VERSION. Omaha has some functionality in it from Google Update related to bug workarounds when upgrading from prior versions, so don't set the VERSION to any lower than in the file omaha\VERSION.

When releasing your fork of Omaha, we recommend starting the version at the initial version in the file omaha\VERSION and version_build+2 (this must be odd). Remember to bump the version up whenever releasing an updated version.

Customizing

• Mandatory changes
• Recommended changes