SKS OpenPGP Keyserver


SKS (Synchronizing Key Server) is a new OpenPGP keyserver developed and maintained by Yaron Minsky. Instead of sending emails to synchronize the keyservers in the network, as the traditional PKS system does, uses SKS a highly efficient and reliable reconciliation algorithm to locate and eliminate differences between keyserver databases. Database changes to one keyserver will be quickly distributed to all other keyservers, and even out-of-date servers or servers with intermittent connectivity will stay fully synchronized with the rest of the steady growing SKS network. Nevertheless is SKS fully compatible to the existing PKS system, it can and does both send and receive syncs from PKS servers ensuring seamless connectivity. SKS also has support for new and old style packets, photoID packets, multiple subkeys, and pretty much everything allowed by RFC2440 and RFC2440bis. SKS is written in Objective Caml.

Note: If you want to link to this server, please use http://keyserver.pramberger.at/.

On this page:

Server Status


Service Status Last Update   Statistics  (more)
Database Image: Online 2010-03-11 01:55 (CET)   Keys 2806790
Synchronisation  Image: Online 2010-03-11 01:55 (CET)   Peerings 18 SKS / 2 PKS
Legend:  Image: Online Online  Image: Maintenance Maintenance  Image: Offline Offline

top

Search Database


Use the form below to search for specific PGP keys. Possible search strings are names, email addresses or hex-formatted key id's (prefixed by 0x). Additional search and format options can be defined using the option fields.


Display options    
Search options      
 
top

Update Database


Use the form below to add your PGP key to the database or update an already existing key in the database, eg. when public signatures are added. The changes are automatically distributed to all keyservers in the SKS and PKS network, there is no need to apply your changes to other keyservers.

Note: The keyserver only accepts key data in ASCII format! The email addresses on your key are distributed as part of it and will be accessible by anyone using the keyserver network. It is possible that someone use this data for malicious purposes, eg. SPAM. It is NOT possible to remove an already published key from the keyserver network!



 
top

HKP Access


It is often easier to let the PGP software interact with keyservers rather than using a web interface to manually search for PGP keys. This interaction is done using HKP (Horowitz Key Protocol), named after Marc Horowitz who developed and operated the first PGP keyserver. HKP is based on HTTP and uses port 11371. Some PGP keyservers provide the same functionality on HTTP port 80 to enable access for users behind restrictive firewalls. Depending on your PGP software use one of this URL's to access this keyserver:

x-hkp://keyserver.pramberger.at
http://keyserver.pramberger.at
http://keyserver.pramberger.at:11371

You can also use a round-robin DNS name to better distribute the load between all active keyservers in the SKS network. In this case use one of this URL's to access a random keyserver:

x-hkp://pool.sks-keyservers.net
http://pool.sks-keyservers.net:11371
top

Email Access


If all else fails you can still access this keyserver sending requests via email. This is called EKP (Email Key Protocol) and is commonly used in the PKS system. Some PGP software has still support for this type of keyserver access. SKS has no builtin support for EKP, so we implemented a special interface on this keyserver which translates the email request to SKS and sends back the results. Use this link to get a list of supported commands. This is the interface email address:

pgp-public-keys@pramberger.at
top

Last Modification: 2009-03-11 23:30 (CET)
© 2005-2010 Peter Pramberger
Client: (IPv4) 38.107.191.98
W3C: XHTML1 | CSS2
Image: Stop Software Patents!

Image: Join the Free Software Foundation!

Image: Irrepressible Campaign