Hockeypuck reads configuration from a TOML-format configuration file.
[hockeypuck] contact=0xF79362DA44A2D1DB hostname=keys.cmarstech.com
These settings are displayed on the stats page (/pks/lookup?op=stats). The
contact field should contain the long key ID or full fingerprint of the
keyserver administrator. The
hostname field should be set to the external
hostname of the server (which may differ from the keyserver host, if
hostname may be used to identify the server in
[hockeypuck] logfile="/path/to/logfile" loglevel=<one of: DEBUG,INFO,WARNING,ERROR,FATAL,PANIC>
If not configured, hockeypuck will log INFO level messages and higher severity to standard error.
Hockeypuck will serve static files from
/ out of the
webroot path, so long as
the path names do not conflict with HKP routed requests (like
index.html will be served by default if the path resolves to a directory and
the file exists.
By default, Hockeypuck will respond to HKP operations
op=stats with an
application/json response. The underlying
structs for these responses can be used in HTML templates of your own design
to customize the output.
Specify these templates with:
[hockeypuck] indexTemplate="/path/to/template" vindexTemplate="/path/to/template" statsTemplate="/path/to/template"
The path must be to a file containing a valid Go html/template.
vindexTemplate operate on a struct containing two top-level fields,
.Query, an instance of the hkp.Lookup request parameters.
.Keys, a slice of jsonhkp.PrimaryKey model structs.
statsTemplate operates on an instance of server.stats.
See the packaged templates for an example.
If storage is not otherwise configured, Hockeypuck defaults to connecting to a
MongoDB server at
localhost:27017. This is effectively:
[hockeypuck.openpgp.db] driver="mongo" dsn="localhost:27017"
dsn field is just the host:port of the MongoDB server.
With MongoDB, Hockeypuck uses database name
hkp and collection name
keys by default. This can be changed with the options:
[hockeypuck.openpgp.db.mongo] db=dbname collection=collection_name
PostgreSQL >= 9.4 is required for use with Hockeypuck, as the JSONB data type is used to store most of the public key material. Some fields are broken out into separate columns for indexing. For details, refer to the PostgreSQL storage backend, pghkp.v1.
To use PostgreSQL:
[hockeypuck.openpgp.db] driver="postgres-jsonb" dsn="database=hkp host=/var/run/postgresql port=5432 sslmode=disable"
See the pq driver package documentation for details on how to construct the connection string.
Hockeypuck supports the SKS reconciliation (recon) protocol.
[hockeypuck.conflux.recon] httpAddr=":11371" reconAddr=":11370"
The above are default settings if not otherwise specified.
httpAddr determines the address that will be advertised to remote peers for
retrieving key material with
reconAddr determines the listen address for the recon server. This is
:11370 among SKS keyservers.
[hockeypuck.conflux.recon.partner.peer1] httpAddr="keys.cmarstech.com:11371" reconAddr="keys.cmarstech.com:11370" [hockeypuck.conflux.recon.partner.peer2] httpAddr="juju-azure-dev-y9157oo521.cloudapp.net:11371" reconAddr="juju-azure-dev-y9157oo521.cloudapp.net:11370"
Create a section for each peer
where peername is a unique logical name given to each peer (it doesn't have to relate
to the hostnames or anything).
Each peer must declare a
reconAddr. These are usually the
same host, but they might differ, especially if the HKP service is
[hockeypuck.conflux.recon] version="1.1.3" # this is default allowCIDRs=["10.0.0.1/8"] # default is  filters=["yminsky.dedup"] # default is 
version is the protocol compatibility version (SKS release version)
advertised to remote peers. Hockeypuck does not use this field.
allowCIDRS is used to allow incoming recon connections from remote addresses
other than the defined peers. This is especially useful when inbound
connections to Hockeypuck are subject to NAT (some cloud providers do this). If
not specified, inbound connections are only allowed from partner IP addresses.
filters are labels that indicate the type of processing that has been applied
to key material. Recent versions of SKS typically require
filters=["yminsky.dedup"], which indicates that duplicate PGP packets have
been dropped from key material. Hockeypuck deduplicates key material
regardless; this field is only used for protocol compatibility with SKS.
The prefix tree is used to keep track of which keys the peer has, for synchronization purposes.
path given should be a writeable directory that already exists.