setuping local/standalone sks keyserver

John Clizbe John at
Tue Aug 3 22:43:42 CEST 2010

Prasanth Thandra wrote:
> On Tue, Jul 20, 2010 at 12:50:53PM +0530, Prasanth Thandra wrote:

I already replied this on July 21, but it would appear it never reached you so
allow me to quote myself in these two top sections (>+)

>> i configured gnupg 2.0.15 on RHEL4 which is a mialserver.
>> i am able to generate keypairs.
>> now i want to setup a keyserver either on localhost or as a standalone.
>> please let me know how to do the same.

>+ Setting up a keyserver is relatively simple, but I'm not reading the use case
>+ for a standalone keyserver. What is it you are wanting to accomplish?
>+ For serving a small number of keys, which is typically the standalone model,
>+ LDAP is more likely the better implementation.

> Start from
> I don't know if anybody has made an RPM of that; probably somebody has,
> but I'm not familiar enough with the various RPM distribution channels
> to check :)

>+ Prebuilt RPMs as well as DEBs of the latest release should be available.*
>+ The nominal place for SKS support is the sks-devel list at sks-devel at
>+ ( )

* A quick google,  returned, near the top,

> HI,
> First i want to thanks Mr. *Peter Pentchev for his first inputs.*
> *i am trying to configure a local sks keyserver on RHEL4.
> *i downloded sks-1.1.1, ocaml-3.11.2 and Berkely DB db-4.6.21
> *i installed the prerequisites **caml-3.11.2 and Berkely DB db-4.6.21 as
> said in README of sks-1.1.1**

It would appear that you stopped reading the README after that section on
installing ocaml. Please read the the full README and continue with the next two
sections (at a minimum):

    * Copy Makefile.local.unused to Makefile.local, and edit to match your

    * Compile

        make dep
        make all
        make all.bc  # if you want the bytecode versions
        make install # puts executables in $PREFIX/bin, as defined
                     # in Makefile.local

> *then i *
> *#CD /../../sks-1.1.1

Typically, it's a directory under /var, /var/sks or /var/lib/sks

> *#mkdir dump

Did you put any keyring files in dump? You mention you wish to run this as a
standalone keyserver, that would imply that you have your own keyrings you wish
to serve.

If you wish to serve the main key database that the online SKS network uses, you
need to download it into the dump directory, presently ~4GB.

Note: that also makes the idea of a standalone server questionable as it will
soon become out of sync with the keys on the public servers.

> *
> === Running fastbuild... ===
> ./ line 11: sks: command not found
> Command failed unexpectedly. Bailing out

1) You need to build the source and install the executables
2) IMO, edit and replace fastbuild with build

> *please help me in resolving the issue.

To repeat myself:

    The nominal place for SKS support is the sks-devel list at
    sks-devel at ( )

Help _IS_ available. You are asking in the wrong place. The is a fair amount of
work involved in setting up SKS -- a full discussion of which is NOT appropriate
to this list.

Subscribe and ask on SKS-Devel.

John P. Clizbe                      Inet: John (a) Gingerbear DAWT net
FSF Assoc #995 / FSFE Fellow #1797  hkp://  or
     mailto:pgp-public-keys at

Q:"Just how do the residents of Haiku, Hawai'i hold conversations?"
A:"An odd melody / island voices on the winds / surplus of vowels"

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 499 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20100803/214d5a18/attachment.pgp>

More information about the Gnupg-users mailing list