PGP keysigning policy

This keysigning policy applies to Asbjørn Sloth Tønnesen’s PGP key 442A4F875238B839.

TL;DR

Most interesting part is likly the description of my signing levels.

0.0 Preamble

Signing policy version: 1.1 (For changelog, see section 6.0).

This OpenPGP/GnuPG key signing policy is applicable to key signing done with the following OpenPGP/GnuPG key:

pub   rsa4096 2009-08-10 [SC] [expires: 2028-10-05]
      9E98 4977 C30D 06BB 2D8C  EC66 442A 4F87 5238 B839

This key can be found on https://asbjorn.st/pgp/442A4F875238B839/key.txt, though it might not have all the newest signatures, so the most up to date will often be my public key on the keys.openpgp.org keyserver.

This policy is to be found at https://asbjorn.st/pgp/442A4F875238B839/policy/ and a signed Markdown version at https://asbjorn.st/pgp/442A4F875238B839/policy/signed.txt.

0.1 Definitions

I, me, my
any references to ‘I’, ‘me’ or ‘my’ refer to Asbjørn Sloth Tønnesen.
keys
in this document, when not explicitly stated otherwise, key or keys refers to PGP/OpenPGP/GnuPG keys.
signee
the person requesting their key to be signed by me, Asbjørn Sloth Tønnesen, using my personal key 442A4F875238B839 (see full fingerprint above).

1.0 Key signing conditions

I only sign keys when I have personally met the person who claims to be the owner of said key. Thus, arranging a meet or attending a keysigning party where I’m present, is a requirement for the signee to get their key signed by me.

2.0 Signing levels

GnuPG supports four different signing levels. Below, all of the different levels are listed, and the requirements for the signee to obtain each level is provided.

sig 0 (0x10)
The regular non-specified signature, used by me only for signing automated, non-personal keys (like organisation or release keys).
sig 1 (0x11)
This is used for personal keys where no ID was verified, but the signed UID’s have been observed used within the relevant community-setting for at least a year, and so signing the UID’s can still help improve the web of trust within the project.
sig 2 (0x12)
‘I have done casual checking’, so used for signing keys checked during keysigning parties, or in other massive and non-relaxed, non-quiet signing meet-ups. While a positive picture ID is required, careful checking was not possible.
sig 3 (0x13)
‘I have done careful checking’, used by me for one-on-one keysigning, where multiple positive ID’s are exchanged and checked for security features based on online indexes of such features.

2.1 Keysigning party modifiers

While keysigning parties are a great way to obtain a lot of signatures, the quality of the signature will be valued less by me.

Usually the setting is not optimal, it is cold and/or really busy and the sheer amount of people attending pressures everyone to quickly continue down the line. Therefore, a sig 2 will be the highest signature given by me.

Furthermore, any uid’s not listed on the keysigning party sheet, will not be signed at all.

I will obtain your key from one of the major keyservers (if the event doesn’t have its own), verify names, email, fingerprint and sign accordingly.

Any additional uid’s that are non-email (and contain anything else than just the name of signee) and/or picture uid’s will not be signed and sent.

2.2 Signing of photo uid’s

Photo uid’s will only be signed for signees I have known for over a year or signees who can provide at least three photo ID’s of which one is goverment issued and bear a strong resemblance to both real life and photo uid.

2.2 Signing of non-email uid’s

Non-email uid’s are not signed by me by default. However, there are some exceptions. First of all, just as with all email uid’s, they have to be present on paper during the meeting. Second, if the uid consists of merely the full name, which is identical to the full name of one or more email uid’s, I will sign. For things such as birth date and location, I will have to have verified those during the meeting.

During a keysigning party there is hardly opportunity to do so, unfortunately, therefore, I will not sign non-email uid’s which I were unable to verify during a keysigning party.

3.0 Meeting in person

Aside from meeting in person during a keysigning party, we can arrange a meeting for one on one for mutual keysigning. I attend quite a few events every year mostly in Europe, but am otherwise based in Copenhagen.

3.1 One on one meetings

When meeting one on one, you will want to bring the following:

4.0 Signing procedure

After meeting in person, I will sign the key which was verified during said meeting, when home. The signing will be done using caff, which extracts the key from a keyring or keyserver.

Therefore, you will want to make sure that the key is present on keyservers and is up to date.

After signing, caff will email your signed public key to each of the uid’s encrypted, if possible. Photo uid’s and non-email uid’s, if signed, will be attached to each email as well.

I reserve the right to not sign a key at my own discretion.

The following sites have more info on my PGP key:

6.0 Changelog

Date Version Changes
2012-06-10 1.0 Version 1.0, initial version, all major sections present
2026-10-13 1.1 Minor update, reformat to Markdown. Fix dead links. Describe and begin using sig 1. Update primary URL, and links.

7.0 Copyright and licensing

The initial version of this document was based on Ewald Tienkamp’s policy (2010).

This document is licensed under the conditions of the Creative Commons BY-NC-SA.

Inspiration for this policy has been drawn from the following (in no particular order):


  1. Which was once available at http://ewald.tienkamp.info/keysigningpolicy.php↩︎