GNU Privacy Guard DNS keyserver client

What is this?

This is a plugin to GNU Privacy Guard to connect to DNS-based key servers.

If you do not know what GnuPG, DNS or DNS-based key servers is, I suggest using the following resources.

• GnuPG homepage
• Specification for DNS-based Certificate distribution
• CKS-DNS, a DNS based OpenPGP keyserver for CKS

News

• 2002-08-05 Wrote an IETF draft documenting how this works
• 2002-08-03 Version 1.2 released.
• 2002-07-07 Version 1.0 released.

Download and Installation

The latest release is available at http://josefsson.org/gpgkeys_jkp/gpgkeys_jkp.

It is a Perl script, and it needs two external libraries:

• Net::DNS v0.24 or later. 0.24 needs a patch. If you use 0.25 or later you don't need to patch it.
• MIME::Base64

After making sure you have installed the libraries, put the script in your $PATH and add the following to your ~/.gnupg/options file:

keyserver jkp://dnskeys.josefsson.org

That's it. If it isn't, it is a bug, please let me know.

You can also grab the tarball, which includes the script, this HTML page and the Net::DNS patch.

Contact information

You can contact the author at [email protected]. Unless the list managers objects, I'd prefer discussion to occur on the gnupg-devel mailinglist.

Features

• Retrieve OpenPGP keys
• Send your own OpenPGP keys to the server
• Using DNS means keys often are cached in DNS caches closer to clients
• Using DNS means there can be many servers in a fail-over fashion throughout the world
• Using DNS often means the closest server in the world is chosen (round-trip calculations made by DNS resolver software)

The server software is CKS and CKS-DNS.

TTY Screenshots

Verifying some data without having the key locally:

bash-2.05a$ gpg < /data1/redhat/MD5SUM
gpg: NOTE: THIS IS A DEVELOPMENT VERSION!
gpg: It is only intended for test purposes and should NOT be
gpg: used in a production environment or with production keys!
gpg: Warning: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
8ea0ba529e62554d15f26d5f46ba6646  limbo-i386-disc1.iso
aa6b2d73c4a7923b3b82cf67b876509f  limbo-i386-disc2.iso
85a84e06bbb16554c41ff055c924be25  limbo-i386-disc3.iso
dc2199c6945c99ee56b81b9df9b19a77  limbo-i386-disc4.iso
8cdd5ab0c19cb5561314a9d4bb391a0f  limbo-i386-disc5.iso
gpg: Signature made Wed Jul  3 05:55:10 2002 CEST using DSA key ID DB42A60E
gpgkeys: requesting key 0x219180CDDB42A60E from x-jkp://dnskeys.josefsson.org:
gpgkeys: key 0xDB42A60E retrieved from dnskeys.josefsson.org
gpg: key DB42A60E: public key "Red Hat, Inc " imported
gpg: Total number processed: 1
gpg:               imported: 1
gpg: Good signature from "Red Hat, Inc "
gpg: checking the trustdb
gpg: checking at depth 0 signed=0 ot(-/q/n/m/f/u)=0/0/0/0/0/1
gpg: next trustdb check due at 2003-05-05
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Fingerprint: CA20 8686 2BD6 9DFC 65F6  ECC4 2191 80CD DB42 A60E
bash-2.05a$

Sending your own key to the keyserver:

bash-2.05a$ gpg --send-keys 5C980097
gpg: NOTE: THIS IS A DEVELOPMENT VERSION!
gpg: It is only intended for test purposes and should NOT be
gpg: used in a production environment or with production keys!
gpg: Warning: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
gpgkeys: sending key 5C980097 to dnskeys.josefsson.org
gpgkeys: trying server latte.josefsson.org
gpgkeys: key 0x5C980097 sent to dnskeys.josefsson.org
bash-2.05a$