Yesterday I did the first release of my OpenPGP compatible keyserver, onak, in 4 years. Actually, 2 releases because I discovered my detection for various versions of libnettle needed some fixing.
It was largely driven by the need to get an updated package sorted for Debian due to the removal of
dh-systemd, but it should have come sooner. This release has a number of clean-ups for dealing with the hostility shown to the keyserver network in recent years. In particular it implements some of dkg’s Abuse-Resistant OpenPGP Keystores, and finally adds support for verifying signatures fully. That opens up the ability to run a keyserver that will only allow verifiable updates to keys. This doesn’t tie in with folk who want to run PGP based systems because of the anonymity, but for those of us who think PGP’s strength is in the web of trust it’s pretty handy. And it’s all configurable to taste; you can turn off all the verification if you want, or verify everything but not require any signatures, or even enable v3 keys if you feel like it.
The main reason this release didn’t come sooner is that I’m painfully aware of the bits that are missing. In particular:
- Documentation. It’s all out of date, it needs a lot of work.
- FastCGI support. Presently you need to run the separate CGI binaries.
- SKS Gossip support. onak only supports the email syncing option. If you run a stand alone server this is fine, but Gossip is the right approach for a proper keyserver network.
0.6.0 - 13th September 2020
- Move to CMake over autoconf
- Add support for issuer fingerprint subpackets
- Add experimental support for v5 keys
- Add read-only OpenPGP keyring backed DB backend
- Move various bits into their own subdirectories in the source tree
- Add support for full signature verification
- Drop v3 keys by default when cleaning keys
- Various code cleanups
- Implement pieces of draft-dkg-openpgp-abuse-resistant-keystore-03
- Add support for a fingerprint blacklist (e.g. Evil32)
- Deprecate the .conf configuration file format
- Drop version info from armored output
- Add option to deny new keys and only allow updates to existing keys
- Various pieces of work removing support for 32 bit key IDs and coping with colliding 64 bit key IDs.
- Remove support for libnettle versions that lack the full SHA2 suite
0.6.1 - 13th September 2020
- Fixes for compilation without nettle + with later releases of nettle