-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 GPG Signing Policy ================== Preamble - -------- This policy is valid for all signatures made by the following GnuPG keys: pub rsa4096 2021-01-01 [SC] DDBFA9DAAFE75FDC05C967ACCD5CC9AFA8A2C927 uid [ultimate] Michael Englehorn sub rsa4096 2021-01-01 [E] [expired: 2023-01-01] sub rsa4096 2021-01-01 [A] [expired: 2023-01-01] sub rsa4096 2023-01-02 [E] [expires: 2024-01-02] sub rsa4096 2023-01-02 [A] [expires: 2024-01-02] These keys will always be available on this page[0], but the most current versions can usually be fetched from keyserver hkp://keys.gnupg.net [1]. This policy was originally written on 2014-08-22 and will be followed from this date on but it may be replaced with a new version at any time. Content and structure of this document are strongly based on the OpenPGP Key Signing Policy of Andres J. Diaz[2] but have been slightly modified from the original sources. Updated: 2023-01-07 - New subkeys Updated: 2022-04-05 - New master key DDBFA9DAAFE75FDC05C967ACCD5CC9AFA8A2C927 replaced CC10C6F7517CC64CFC4BA9D97502F475E7B6CCB9 due to it expiring. - Also, I moved. Updated: 2018-10-16 - New subkeys. Starting to deprecate RSA keys. Updated: 2017-05-02 - Removed expired subkeys. Updated: 2016-10-15 - New Subkeys, changed text from "outside the European Union" to "outside the United States". Updated: 2015-11-16 - New Subkeys, no other changes. Old policy available at: http://michael.englehorn.com/gpg/policy-2014-08-22.txt Location - -------- I live in Blaine, MN (USA) and I am open to sign keys at any time. The easiest way for verifying keys would be to write me an e-mail and arrange a meeting in the area around Minneapolis, MN or Blaine, MN. Another opportunity to get in personal contact would be to address me at certain computer related events. Prerequisites for signing - ------------------------- The signee (the key owner who wishes to obtain a signature to his/her key from me, the signer) must make his/her OpenPGP key available on a publicly accessible keyserver (see above for example keyservers). The signee's key schould have at least a key size of 2048 bits. The signee must prove his/her identity to me by way of a valid identity card or driving licence. These documents must feature a photographic picture of the signee. No other kind of documents will be accepted. This also implies that the signee’s key must feature his/her real name in order to be checked up on his/her identity card. A key which only contains a pseudonym will not be signed. For people from outside the United States I will check both of these two tokens (since I cannot assess their risk of fraud). Exceptions may be made if there is a good reason for me to do so. The signee should have prepared a strip of paper with a printout of the output: ~ gpg --fingerprint 0x12345678 (or an equivalent command if the signee does not use GnuPG) where 0x12345678 is the key ID of the key which is to be signed. A handwritten piece of paper featuring the fingerprint and all UIDs the signee wants me to sign will also be accepted. The above must take place under reasonable circumstances (i.e. ourselves not being in a hurry, exchanging key data at a calm place and so on). The act of signing - ------------------ After having received (or exchanged) the proof detailed in the above I will sign the signee’s piece of paper myself to avoid fraud. At home I will sign the UIDs which I was asked to sign. Each signature will then be mailed separately to the corresponding mail address of the single UIDs. Depending on the character of the key which is to be signed by me I will use different levels of signatures: Levels of signatures - -------------------- Here are the levels of trust that I can give to my signatures: Level 3: A level of 3 is given to sign-and-encrypt keys: I have met the signee, I have verified his/her identity card and fingerprint and I was able to send my signatures encrypted with the corresponding key of the signee. These signatures are the strongest in my web of trust. Photographic UIDs are also going to be signed with a level of 3 if I can still remember the signee’s face when I will be back at home. Level 2: A level of 2 is given to sign-only keys. It is not clear to determine if the owner of the mail account is the same as the key owner because encryption cannot be used, hence the signatures only receive a lower level of 2. Level 1: A level of 1 will never be used by me for it weakens the web of trust in my opinion. I have never signed keys without appropriate verification and I will never do so in the future. Level 0: A level of 0 is given to keys of Certification Authorities since in most cases the key owner is a whole organization and not a single person. Usually the fingerprints of those keys have to be verified by getting them from the corresponding website of the CA and cannot be checked by exchange with a member of the CA who is in charge. These signatures are the weakest in my web of trust. [0] http://michael.englehorn.com/gpg/pub.asc [1] http://keys.gnupg.net/ [2] http://ajdiaz.wordpress.com/gpg-signing-policy/ -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE3b+p2q/nX9wFyWeszVzJr6iiyScFAmS2giIACgkQzVzJr6ii ySelWxAAuoYKbk7KrDweAPSeQuU0Dfv/E4tNRxXX6IAN0WZF1GZFrxRBe2XOGmBL /dXWKWWPixURB/Rx8mLcaiBJtJMu63jhK2AkePBdqDTW65W6MtfURXz5UOSBcf3b 0yYkR5ADHF/5JVpbqQKCaVv1BiBKvf2nTe3n7jEVZ36bpBSVDtqkYjZGFTORavOX xt9cKRbMKQGdo3ZsBWyJ3u5hfmscMi1Z6EYP4cFVk6c8NRKubR9ReB7jJxiXf61Z YdqyrFKVXdCgOKzri/rXgGdnC2q0Q8NK510R73kjBRdf6LvlXBoecSG1UUQtHM+y LW5Xi2peQCpALyfRwGClC6EP3/g7RmQ+i2pR6IvzyM5bPykxyqEKYmEF9ofd0+UW urOaNr81AWnLjQYluad6moqeem8u0mq0BjoTw1Ii0m0j+NA5iZzA6R2vHVRMKb0f 5guQgBpWTrjqEQwsgHd40w6uR3OBW5EOhEcA9XAFRG4Ky/W+2qYUzqq6eWWdBBmK A11MpV9C+iq2adR1wYiPu1yXvz74r8gfwNfEW9bsZxa87y2JToBfEF7Vtj778MC0 ieCECgVhTooF9S6vdLLmJAuNa91lUfADh+Aoo98bO16hvKLe2mg4aQtmo80K87mw rIQ7PCIpBCMXX870XuGdMDZnSLVNLxcKMUqdYbThKLwz8n6YU5E= =fYCV -----END PGP SIGNATURE-----