sks-keyserver /

Filename Size Date modified Message
bdb
sampleConfig
sampleWeb
132 B
170 B
235 B
5.9 KB
1.9 KB
8.0 KB
246 B
17.7 KB
11.4 KB
172 B
8.2 KB
5.1 KB
1.3 KB
1.9 KB
2.5 KB
6 B
2.8 KB
49 B
4.8 KB
147 B
5.1 KB
4.0 KB
9.0 KB
1.1 KB
8.0 KB
5.0 KB
238 B
4.4 KB
2.5 KB
4.5 KB
121 B
12.6 KB
5.2 KB
12.8 KB
58 B
7.5 KB
993 B
8.2 KB
1.9 KB
2.5 KB
127.8 KB
8.4 KB
1.4 KB
2.2 KB
28.6 KB
57 B
2.7 KB
5.8 KB
270 B
7.1 KB
4.1 KB
749 B
8.5 KB
7.5 KB
7.4 KB
6.1 KB
853 B
2.3 KB
3.9 KB
346 B
4.6 KB
4.7 KB
1.8 KB
3.8 KB
456 B
4.0 KB
22.1 KB
2.2 KB
2.0 KB
4.9 KB
1.5 KB
3.2 KB
125 B
9.1 KB
45.2 KB
10.1 KB
2.0 KB
2.7 KB
4.1 KB
2.1 KB
9.3 KB
3.1 KB
6.3 KB
2.4 KB
1.7 KB
4.4 KB
8.0 KB
2.4 KB
5.3 KB
2.8 KB
2.3 KB
4.1 KB
915 B
5.2 KB
2.5 KB
2.4 KB
6.0 KB
5.5 KB
10.7 KB
6.5 KB
6.2 KB
11.4 KB
2.6 KB
12.3 KB
1.4 KB
4.4 KB
4.7 KB
6.2 KB
1.0 KB
3.7 KB
33.0 KB
1.1 KB
6.4 KB
3.8 KB
179 B
2.5 KB
149 B
5.2 KB
3.5 KB
2.3 KB
3.3 KB
1.6 KB
3.1 KB
6.0 KB
1.2 KB
1.9 KB
124 B
6.8 KB
717 B
4.6 KB
218 B
8.0 KB
1.1 KB
1.6 KB
1.3 KB
13.7 KB
1.2 KB
4.1 KB
571 B
3.8 KB
316 B
4.4 KB
477 B
2.0 KB
233 B
16.7 KB
4.0 KB
6.5 KB
689 B
14.7 KB
4.1 KB
6.4 KB
35 B
9.3 KB
537 B
1.5 KB
2.7 KB
3.2 KB
5.9 KB
848 B
4.8 KB
7.5 KB
765 B
4.1 KB
1.8 KB
2.1 KB
5.0 KB
6.5 KB
10.6 KB
1.8 KB
2.3 KB
82 B
14.0 KB
1.4 KB
5.8 KB
4.8 KB

SKS Keyserver

The following is an incomplete guide to compiling, setting up and using SKS. The documentation still needs work, but hopefully this is enough to get you started.

Prerequisites

There are a few prerequisites to building this code. You need:

Verifying the integrity of the download

Releases of SKS are signed using the SKS Keyserver Signing Key available on public keyservers with the KeyID

0x41259773973A612A

and has a fingerprint of

C90E F143 0B3A C0DF D00E 6EA5 4125 9773 973A 612A.

Using GnuPG, verification can be accomplished by, first, retrieving the signing key using

gpg --keyserver pool.sks-keyservers.net --recv-key 0x41259773973A612A

followed by verifying that you have the correct key

gpg --keyid-format long --fingerprint 0x41259773973A612A

should produce:

pub   4096R/41259773973A612A 2012-06-27
Key fingerprint = C90E F143 0B3A C0DF D00E 6EA5 4125 9773 973A 612A

A check should also be made that the key is signed by trustworthy other keys;

gpg --list-sigs 0x41259773973A612A

and the fingerprint should be verified through other trustworthy sources.

Once you are certain that you have the correct key downloaded, you can create a local signature, in order to remember that you have verified the key.

 gpg --lsign-key 0x41259773973A612A

Finally; verifying the downloaded file can be done using

gpg --keyid-format long --verify sks-x.y.z.tgz.asc

The resulting output should be similar to

gpg: Signature made Wed Jun 27 12:52:39 2012 CEST
gpg:                using RSA key 41259773973A612A
gpg: Good signature from "SKS Keyserver Signing Key"

Compilation and Installation

  • Install OCaml and Berkeley DB

    When installing ocaml, make sure you do both the make world and the make opt steps before installing. The later makes sure you get the optimizing compilers. (do make opt.opt if you want faster compilation. You can then set the environment variables OCAMLC, OCAMLOPT and CALMP4O to ocamlc.opt, ocamlopt.opt and camlp4o.opt respectively.)

    If your vendor or porting project supplies prebuilt binaries and libraries for Berkeley DB, make sure to get the development package as you will need the correct version include files.

  • Copy Makefile.local.unused to Makefile.local, and edit to match your installation.

  • 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
    

    There are some other useful compilation targets, mostly useful for development.

    • make doc

      creates a doc directory with ocamldoc-generated documentation of the individual modules. These are mostly useful as documentation to the source code, not a user's guide.

    • make modules.ps

      Creates a ps-file that shows the dependencies between different modules, and gives you a sense of the overall structure of the system. For this to work you need to have AT&T's graphviz installed, as well as python2. The python script that's used actually requires that python2 be called python2, rather than python. You can of course edit that script.

Setup and Configuration

You need to set up a directory for the SKS installation. It will contain the database files along with configuration and log files.

Configuration options can be passed in on the command-line or put in the sksconf file in the SKS directory. the -basedir option specifies the SKS directory itself, which defaults to the current working directory.

Sksconf and commandline options

The format of the sksconf file is simply a bunch of lines of the form:

keyword: value

The # character is used for comments, and blank lines are ignored. The keywords are just the command-line flags, minus the initial -.

The one thing you probably want no matter what is a line that says

logfile: log

which ensures that sks will output messages to recon.log and db.log respectively.

Membership file

If you want your server to gossip with others, you will need a membership file which tells the sks recon who else to gossip with. The membership file should look something like:

epidemic.cs.cornell.edu 11370
athos.rutgers.edu 11370
...

This file should be called membership, and should be stored in the SKS directory. Note that in order for synchronization to work, both hosts have to have each other in their membership lists. Send mail to sks-devel@nongnu.org to get other SKS administrators to add you to their membership lsits.

IMPORTANT NOTE: if you include the server itself in the membership file, you should make sure that you also specify the hostname option, and that the selected hostname is exactly the same string listed in the membership file. Otherwise, the sks recon will try to synchronize with itself and will deadlock.

Outgoing PKS synchronization: mailsync file

The mailsync file contains a list of email addresses of PKS keyservers. This file is important, because it ensures that keys submitted directly to an SKS keyserver are also forwarded to PKS keyservers.

IMPORTANT: don't add someone to your mailsync file without getting their permission first!

In order for outgoing email sync's to work, you need to specify a command to actually send the email out. The default is sendmail -t -oi, but you may need something different.

Incoming PKS synchronization

Incoming PKS synchronization is less critical than outgoing, since as long as some SKS server gets the new data, it will be distributed to all. Having more hosts receive the incoming PKS syncs does, however, increase the fault-tolerance of the connection between the two systems.

In order to get incoming mail working, you should pipe the appropriate incoming mail to the following command via procmail:

sks_add_mail sks_directory_name

Here's an example procmail entry:

PATH=/path/of/sks/exectuables

:0
* ^Subject: incremental
| sks_add_mail sks_directory_name

Built-in webserver

You can server up a simple index page directly from the port you're using for HKP. This is done by creating a subdirectory in your SKS directory called web. There, you can put an index file named index.html, index.htm, index.xhtm, or index.xhtml, supporting files with extensions .css, .es, or .js, and some image files with extensions jpg, jpeg, png or gif. Subdirectories will be ignored, as will filenames with anything other than alphanumeric characters and the '.' character. This is particularly useful if you want to run your webserver off of port 80. This can be done by using the -hkp_port command-line option.

Building up the databases

  • First, you need to get a keydump. If you're running a PKS server, you should be able to convince PKS to generate one for you. If you're starting from scratch, you'll need to download one from the net. You should contact the pgp keyserver list pgp-keyserver-folk@flame.org

  • in the SKS directory, put in a subdirectory called dump which contains the keydump files from which the database is to be built.

  • Run sks_build.sh. That script actually runs three utilities. You might want to edit sks_build.sh if you want to trade off speed for space usage. At the current settings, you could run out of ram if you try this with less then 256 megs of RAM.

DO NOT DELETE THE dump DIRECTORY, even after the database is built. The original keys are not copied to the database, and so the dump must be left in place.

Platform specific issues

FreeBSD

On FreeBSD it appears that libdb is named differently than on some other platforms. For that reason, you need to set the LIBDB environment value to -ldb46 instead of -ldb-4.6 for other platfomrs.

Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.