graven.dev/public/emelie/pgp/policy.html

55 lines
3.3 KiB
HTML
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>policy</title>
<style>
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
ul.task-list{list-style: none;}
.display.math{display: block; text-align: center; margin: 0.5rem auto;}
</style>
<link rel="stylesheet" href="../../static/style.css" />
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<h1 id="pgp-key-signing-policy-of-emelie-graven">PGP Key signing policy of Emelie Graven</h1>
<h2 id="key-covered-by-this-policy">Key covered by this policy</h2>
<pre><code>pub ed25519 2021-09-27 [SC]
16D36E7BFBB00641BBF6574D9DEBB56FE610BAD1
uid [ultimate] Emelie Graven &lt;emelie@graven.dev&gt;
uid [ultimate] Emelie Graven &lt;emelie@graven.se&gt;
sub ed25519 2021-09-27 [S]
sub cv25519 2021-09-27 [E] [expires: 2023-03-06]
sub ed25519 2021-09-27 [A] [expires: 2023-03-06]</code></pre>
<h2 id="certification-levels">Certification levels</h2>
<p>I use three levels of certification when signing keys. Each certification level also encompasses the requirements of levels below it.</p>
<ul>
<li><p>Level 0 (Generic certification) This type of signature is used to certify that the key holder is in control of the email address of the UID in question. No assertations are made about the key holders identity.</p></li>
<li><p>Level 2 (Casual certification) This type of signature is used to certify that identity of the key holder has been verified with at least one form of government-issued photo ID, or another equally secure means of identification.</p></li>
<li><p>Level 3 (Positive certification) This type of signature is used to certify that the key holder is a person I trust and know personally, or that someone I know personally has vouched for their identity.</p></li>
</ul>
<h2 id="signing-process">Signing process</h2>
<p>Steps 1 through 2 are only required for casual and positive certification, steps 3 through 5 are always required.</p>
<ol type="1">
<li>The signees identity is verified according to the requirements.</li>
<li>The signee gives me a physical copy of their key fingerprint, or in the case of verification over video chat, the fingerprint is supplied verbally.</li>
<li>The signee sends me a signed email from each email address corresponding to a UID they want signed.</li>
<li>I will reply to each email with the signed key in encrypted form.</li>
<li>The signee decrypts the signed keys and optionally publishes them.</li>
</ol>
<h2 id="general">General</h2>
<p>I appreciate if anyone whose keys I sign would return the favour and sign my keys in accordance with their own signing policy.</p>
<p>A signed markdown version of this document can be found <a href="policy.md.asc">here.</a></p>
<h2 id="changelog">Changelog</h2>
<p>2021-11-21: Initial release</p>
</body>
</html>