60 lines
3.2 KiB
Handlebars
60 lines
3.2 KiB
Handlebars
{{#> layout }}
|
|
<div class="about">
|
|
<center><h2><a href="/about">About</a> | <a href="/about/news">News</a> | <a href="/about/usage">Usage</a> | <a href="/about/faq">FAQ</a> | <a href="/about/stats">Stats</a> | <a href="/about/privacy">Privacy</a></h2></center>
|
|
|
|
<h3>Profile pages</h3>
|
|
|
|
<p>
|
|
<span class="brand">keys.openpgp.org</span> displays profile pages for verified e-mail addresses.
|
|
The profile page displays all verified e-mails as well as name taken from the
|
|
key as well as the key fingerprint.
|
|
</p>
|
|
|
|
<p>Each profile page is reachable via <b>https://keys.openpgp.org/<i>email</i></b>
|
|
links e.g. <b>https://keys.openpgp.org/john@example.com</b></p>
|
|
|
|
<h3>Social proofs</h3>
|
|
|
|
<p>
|
|
Additionally to e-mail addresses and basic key info <span class="brand">keys.openpgp.org</span> displays
|
|
and verifies Social Proofs embedded in keys.
|
|
</p>
|
|
|
|
<h3>Adding social proofs</h3>
|
|
|
|
<p>
|
|
The process is two step: first creating or modifying an entry on social site (e.g. Gist on Github
|
|
or profile info on Mastodon) then adding the entry URL to key as a notation.
|
|
The notation uses <code>proof@keys.openpgp.org</code> key (note that due to compatibility reasons
|
|
<code>proof@metacode.biz</code> notation keys are also supported).
|
|
</p>
|
|
|
|
<h3>Supported proofs</h3>
|
|
|
|
<ul>
|
|
<li>Github: Gist containing text <code>[Verifying my OpenPGP key: openpgp4fpr:FINGERPRINT]</code>
|
|
within an <code>openpgp.md</code> file. See <a href="https://gist.github.com/wiktor-k/389d589dd19250e1f9a42bc3d5d40c16">example</a>.</li>
|
|
<li>Mastodon: Add a property in user profile settings that contains your key fingerprint.
|
|
See <a href="https://fosstodon.org/@yarmo">example</a>.</li>
|
|
<li>HackerNews: Add <code>[Verifying my OpenPGP key: openpgp4fpr:FINGERPRINT]</code> to your HackerNews profile.
|
|
See <a href="https://news.ycombinator.com/user?id=wiktor-k">example</a>. Note that you need at least 2 points of
|
|
karma (this is HackerNews API limitation).</li>
|
|
<li>Reddit: Add new post containing <code>[Verifying my OpenPGP key: openpgp4fpr:FINGERPRINT]</code> on your
|
|
own user page space. See <a href="https://www.reddit.com/user/wiktor-k/comments/bo5oih/test/">example</a>.
|
|
Note that currently Reddit proofs fail to verify in Firefox due to a
|
|
<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1235978">bug in Tracking Protection</a>.</li>
|
|
</ul>
|
|
|
|
<h3>Adding proof to OpenPGP key</h3>
|
|
<p>Edit your key with <code>gpg --edit-key FINGERPRINT</code> and enter <code>notation</code> command.
|
|
The notation should be <code>proof@keys.openpgp.org=URL</code> where URL is the link to your proof created in the previous step.</p>
|
|
<p>If you have multiple proofs repeat the <code>notation</code> command as necessary.</p>
|
|
<p>After saving key changes with <code>save</code> use the following command to update your key:</p>
|
|
<blockquote>
|
|
gpg --export your_address@example.net | curl -T - {{ base_uri }}
|
|
</blockquote>
|
|
|
|
<p>See <a href="/wiktor@metacode.biz">this profile page</a> for an example on how proofs are rendered.</p>
|
|
</div>
|
|
{{/layout}}
|