Signed package repositories

Install the tools.
Keep them current.

ChapelTech publishes packages from the projects’ versioned GitHub releases through signed APT and DNF repositories at repo.chapeltech.uk.

Current repositories

APT

Debian 13 · Trixie

Component main, built for amd64 and arm64.

https://repo.chapeltech.uk/debian

DNF

Enterprise Linux 9

Signed RPM packages and repository metadata for x86_64.

https://repo.chapeltech.uk/rpm/el9/$basearch

Verify the repository key

Both repositories use the same OpenPGP certificate. Compare the complete primary fingerprint before installing it; spacing and letter case are insignificant.

ChapelTech Package Repository <repo@chapeltech.uk>

DBDE D585 C6A4 CC17 9E45
77BE 80B0 DB25 BE16 C7EF
Primary key
Expires 2 August 2036
Signing subkey
Expires 4 August 2029

Configure APT

Download the key first, inspect its fingerprint, and only then install the key and supplied deb822 source configuration.

curl -fsSL \
  https://repo.chapeltech.uk/keys/chapeltech-archive-keyring.gpg \
  -o /tmp/chapeltech-archive-keyring.gpg

gpg --show-keys --with-fingerprint \
  /tmp/chapeltech-archive-keyring.gpg

sudo install -d -m 0755 /etc/apt/keyrings
sudo install -m 0644 \
  /tmp/chapeltech-archive-keyring.gpg \
  /etc/apt/keyrings/chapeltech-archive-keyring.gpg

curl -fsSL \
  https://repo.chapeltech.uk/config/chapeltech.sources \
  -o /tmp/chapeltech.sources

sudo install -m 0644 \
  /tmp/chapeltech.sources \
  /etc/apt/sources.list.d/chapeltech.sources

sudo apt update
sudo apt install knc

The source file uses Signed-By and does not modify the system-wide APT trust store. Inspect chapeltech.sources.

Configure DNF

Install the supplied repository definition. When DNF offers to import the key, compare its complete fingerprint with the trust anchor above.

curl -fsSL \
  https://repo.chapeltech.uk/config/chapeltech.repo \
  -o /tmp/chapeltech.repo

sudo install -m 0644 \
  /tmp/chapeltech.repo \
  /etc/yum.repos.d/chapeltech.repo

sudo dnf makecache
sudo dnf install knc

Package signatures and repository metadata signatures are both required.Inspect chapeltech.repo.

Repository indexes and configuration are served from the package repository. Versioned package downloads redirect to the corresponding immutable assets attached to each project’s GitHub release.

Open the repository