I've set up an SKS 1.1.1 keyserver (with db-5.0.21) at the static IP
address 18.104.22.168 (also known as "keys.n3npq.net" and "keys.pmman.com")
and am looking for peers:
keys.n3npq.net 11370 # Jeff Johnson <[hidden email]>
The server is collocated (in Columbus OH USA iirc) and likely has a Very
Big Pipe attached (if that matters). The keydump used was from
yesterday, downloaded from
and the store appears to be synchronized and up-to-date.
It will take another week or so to stabilize "keys.n3npq.net"
and ensure reliable availability, and turn on IPv6, mail forwarding,
and add a web page, all of which is intended, just not quite
The usage case for keys.n3npq.net (and keys.rpm5.org) is to automate *.rpm
package signature verification pubkey retrieval through hkp://, integrating
the SKS KDB schema with a Berkeley DB rpmdb, and to look carefully at the
set reconciliation algorithm for use with not only pubkey servers, but also
*.rpm package repository metadata.
I also hope to permit dual SQL/CRUD access to the underlying database
store using db-5.0.21.