tufup 0.2.0

Automated updates for stand-alone Python applications, built upon python-tuf.

tufup

A simple software updater for stand-alone Python applications.

The tufup package is built on top of python-tuf, which is the reference implementation for TUF (The Update Framework).

The initial implementation is focused on Windows and macOS. The package can be used on other platforms, but these are not actively supported.

About

The tufup package was inspired by PyUpdater, and uses a general approach to updating that is directly based on PyUpdater's implementation.

However, whereas PyUpdater implements a custom security mechanism to ensure authenticity (and integrity) of downloaded update files, tufup is built on top of the security mechanisms implemented in the python-tuf package, a.k.a. tuf. By entrusting the design of security measures to the security professionals, tufup can focus on high-level tools.

Although tuf supports highly complex security infrastructures, see e.g. PEP458, it also offers sufficient flexibility to allow application developers to tailor the security level to their use case. For details and best practices, refer to the tuf docs.

Based on the intended use, the tufup package supports only the top-level roles offered by tuf. At this time we do not support delegations.

Overview

Borrowing tuf terminology, we have tools for the repository (repo) side and tools for the client side.

The repo tools are used by the app developer to:

• create update files (e.g. using PyInstaller)
• sign the resulting files (cryptographically)
• deploy these files to a server

The client tools are used by the app itself to:

• check for updates
• download update files
• apply the update files

The tuf package is used under the hood to check for updates and download update files in a secure manner, so tufup can safely apply the update. See the tuf docs for more information.

Archives and patches

Tufup works with archives (e.g. gzipped PyInstaller bundles) and patches (binary differences between subsequent archives). Each archive, except the first one, must have a corresponding patch file.

Archive filenames and patch filenames follow the pattern

<name>-<version><suffix>

where name is a short string that may contain alphanumeric characters, underscores, and hyphens, version is a version string according to the PEP440 specification, and suffix is either '.tar.gz' or '.patch'.

Patches are typically smaller than archives, so the tufup client will always attempt to update using one or more patches. However, if the total amount of patch data is greater than the desired full archive file, a full update will be performed.

How updates are created (repo-side)

When a new release of your application is ready, the following steps need to be taken to enable clients to update to that new release:

1. Create an application archive for the new release (e.g. a zipped PyInstaller bundle).
2. Create a patch from the current archive to the new archive.
3. Add hashes for the newly created archive file and patch file to the tuf metadata.
4. Sign the modified tuf metadata files.
5. Upload the new target files, i.e. archive and patch, and the updated metadata files, to the update server.

The signed metadata and hashes ensure both authenticity and integrity of the update files (see tuf docs). In order to sign the metadata, we need access to the private key files for the applicable tuf roles.

The tufup.repo module provides a convenient way to streamline the above procedure, based on the tuf basic repo example.

How updates are applied (client-side)

Updates are applied by replacing all files in the current app installation path with files from the latest archive. The latest archive is either downloaded in full (as described above), or it is derived from the current archive by applying one or more downloaded patches. Once the latest archive is available, it is decompressed to a temporary location. From there, a script is started that clears the current app installation dir, and moves the new files into place. After starting the script, the currently running process will exit.

Migrating from other update frameworks

Here's one way to migrate from another update framework, such as pyupdater, to tufup:

1. Add tufup to your main application environment as a core dependency, and move pyupdater from core dependencies to development dependencies.
2. Replace all pyupdater client code (and configuration) in your application by the tufup client.
3. Initialize the tufup repository, so the root metadata file root.json exists.
4. Modify your PyInstaller .spec file (from PyUpdater) to ensure that the root.json file is included in your package.
5. Build, package, and sign using pyupdater, and deploy to your server, as usual. This ensures that your pyupdater clients currently in the field will be able to update to the new tufup client.
6. From here on, new updates will be deployed using tufup.
7. If you want to enable a patch update from the pyupdater version to the new tufup version, extract the latest PyUpdater archive and add the resulting bundle to the tufup repository.
8. To skip patch creation, just create a new app bundle and add that to the tufup repository.
9. BEWARE: Keep the pyupdater repository in place as long as necessary to allow all clients to update.
10. From now on, build, package, sign and deploy using tufup, as described elsewhere in this document.

Platform support

The tufup package is aimed primarily at Windows and macOS applications.

Although tufup could also be used for Linux applications, those are probably better off using native packaging solutions, or solutions such as Flatpak or Snapcraft. Read the Python packaging overview for more information.

The tufup.repo functionality is platform independent, as it is just a thin layer on top of python-tuf. Platform dependence for tufup.client is mainly related to file handling and process handling during the installation procedure. A custom, platform dependent, installation procedure can be specified via the optional install argument for the Client.update() method.