mirrors/hockeypuck
1
0
Fork 0
mirror of https://github.com/hockeypuck/hockeypuck.git synced 2025-12-17 08:55:43 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
Page: Home
Pages
HIP 000: Hockeypuck Improvement Proposals HIP 001: [REVERTED] Regaining control over public key identity with authenticated key management HIP 002: SKS v2 protocol HIP 003: Timestamp aware merge strategy HIP 004: Third party revocation sig distribution HIP 005: Reliable personal data deletion using self signatures HIP 006: WKD support HIP 007: Recursive resolver HIP 008: Out of Band Email Ownership Proof HIP 009: Management Interface HIP 010: Internal rate limiting support HIP 011: Merge ptree into pghkp HIP 012: Define and use JSON‐LD schemas HIP 013: In‐Band Metadata Sync Using Trust Packets Home Migrating from SKS‐keyserver to Hockeypuck Semantic Versioning Policy Upgrading docker‐compose standalone deployment from 2.1 to 2.2
12 Home
Andrew Gallagher edited this page 2025-12-08 00:06:14 +00:00
Table of Contents

NEWS

We are pleased to announce the release of Hockeypuck 2.3.

Hockeypuck is a modern synchronising keyserver that is optimised for ease of deployment, particularly in containerised environments via docker-compose.

Hockeypuck 2.3

Hockeypuck 2.3 is primarily a technical-debt release, but also adds features to ease the upgrade process in a production environment.

Features

There are no breaking changes between the 2.2 and 2.3 branches, and SKS sync is supported between 2.2 and 2.3 peers.

The 2.3 release adds support for online reindexing of the database schema, and offline dump-less reloading of the dataset. Reindexing is enabled by default, and will ensure that the schema is always updated to the latest version. Offline dump-less reload is implemented by a separate utility, hockeypuck-reload - see https://hockeypuck.io/upgrading.html#TOC_1.2. for instructions.

Due to changes in the database schema, it is strongly recommended to upgrade to 2.3 as soon as possible. Hockeypuck 2.4 will be released in early 2026, and will require the new schema to support RFC9580 and HKPv2.

2.3 also adds support for PKS-over-email and PKS-over-HTTP unidirectional sync. This is not enabled by default - see https://hockeypuck.io/configuration.html#TOC_1.4.1. and https://hockeypuck.io/configuration.html#TOC_1.5. for configuration details.

Hockeypuck 2.3 development is kindly supported by NGI Zero Core.

Installation and upgrading

You can install it by cloning the repo from https://github.com/hockeypuck/hockeypuck and checking out the branch branch-2.3, then following the instructions in the README.md file. You should not deploy from the master branch or the latest docker image in production.