myriation/keyoxide-web
1
0
Fork 0
forked from Mirrors/keyoxide-web
Code Pull requests Activity

Add guides

Browse source
This commit is contained in:
Yarmo Mackenbach 2020-06-29 18:02:08 +02:00
parent 66dc368f80
commit 34a506e965
6 changed files with 55 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
pages/guides/openpgp-proofs.content.html Normal file
View file

@ -0,0 +1,26 @@
<h3>Decentralized OpenPGP identity proofs</h3>
<p>Decentralized OpenPGP identity proofs are the brainchild of Wiktor who wrote the original guide on <a href="https://metacode.biz/openpgp/proofs">his website</a> (a suggested read to get first-hand information).</p>
<p>Unlike proofs provided by for example <a href="https://keybase.io">Keybase</a>, OpenPGP proofs are stored inside the PGP keys themselves instead of being mere signatures. Since this operation requires keys with "certify" capabilities and not simply "sign" capabilities, these OpenPGP proofs could be considered more secure.</p>
<h3>What an OpenPGP proof looks like</h3>
<p>Every OpenPGP identity proof is stored in the PGP key as a notation that looks like this:</p>
<code>proof@metacode.biz=https://twitter.com/USERNAME/status/1234567891234567891</code>
<p>This particular proof is for a Twitter account (read more in the <a href="/guides/twitter">Twitter guide</a>). Let's analyse the notation:</p>
<ul>
<li><strong>proof</strong> means the current notation is for an identity proof.</li>
<li><strong>@metacode.biz</strong> is the domain of the person who came up with OpenPGP proofs and serves as a namespace for the notation. The domain is included and used for all proofs to comply with the <a href="https://tools.ietf.org/html/rfc4880#section-5.2.3.16">OpenPGP Message Format standard (RFC 4880)</a>.</li>
<li><strong>https://twitter.com/USERNAME/status/1234567891234567891</strong> is the value of the notation. It is a link to the piece of online content that contains a pre-defined message which must always include the fingerprint of the PGP key that will hold the proof.</li>
</ul>
<p>The proof should always link to a document that can be parsed as JSON to make the verification easy and feasible by the browser. Sometimes however, due to CORS restrictions or API requirements (as is the case for Twitter), no such link is provided by the platform. In these rare exceptional cases, the verification process is delegated to the Keyoxide server which will communicate directly with the platform's servers to get the content of the post.</p>
<h3>Your turn</h3>
<p>If you'd like to add decentralized OpenPGP identity proofs to your key, go to the <a href="/guides">guides</a> and find the right one for your platform of choice. You may find the process to be remarkably easy.</p>
<p>If your platform is not in the list of <a href="/guides">guides</a>, it's not supported yet. See the <a href="/guides/contributing">contributing guide</a> for more information on how to get that platform supported.</p>

1
pages/guides/openpgp-proofs.title.html Normal file
View file

@ -0,0 +1 @@
How OpenPGP identity proofs work

21
pages/guides/proofs.content.html Normal file
View file

@ -0,0 +1,21 @@
<p>Let's see how to verify identity proofs.</p>
<h3>Obtain a public key for verification</h3>
<p>The idea is that anyone can add identity proofs of various platforms in their keys. Since this information is kept in the public key, you could take anyone's public key and check whether they indeed have control over the accounts they claim to.</p>
<p>If you already have a public key (or its fingerprint) with OpenPGP identity proofs you would like to use to verify, great! If not, you could use the following fingerprint:</p>
<code>9f0048ac0b23301e1f77e994909f6bd6f80f485d</code>
<h3>Verify proofs</h3>
<p>Open the <a href="/proofs" target="_blank">keyoxide.org/proofs</a> page and paste the fingerprint in the <strong>Email / key id / fingerprint</strong> field. Scroll down and press the <strong>VERIFY PROOFS</strong> button.</p>
<p>You now see a list of domains and/or accounts on platforms for which the owner of the public key claims to have an control over.</p>
<p>If the last link on a line says <strong>proof</strong>, the proof could not be verified for any number of reasons but Keyoxide still allows to check the supposed proof and decide for yourself whether you trust the claim. If the </p>
<p>If the last link on a line says <strong>verified</strong>, the owner of the public key indeed has shown beyond doubt that it has control over the domain or account.</p>
<h3>Your turn</h3>
<p>If you'd like to add decentralized OpenPGP identity proofs to your key, go to the <a href="/guides">guides</a> and find the right one for your platform of choice. You may find the process to be remarkably easy.</p>
<p>If your platform is not in the list of <a href="/guides">guides</a>, it's not supported yet. See the <a href="/guides/contributing">contributing guide</a> for more information on how to get that platform supported.</p>

1
pages/guides/proofs.title.html Normal file
View file

@ -0,0 +1 @@
Verifying identity proofs

5
pages/guides/selfhosting-keyoxide.content.html Normal file
View file

@ -0,0 +1,5 @@
<p>Though it's not a fully supported use case yet, anyone can take the <a href="https://codeberg.org/yarmo/keyoxide">source code</a> and put it on their own server. The idea is that <a href="https://keyoxide.org">Keyoxide.org</a> is not special in itself. After all, all the heavy lifting is done by the browser. So the role of any individual Keyoxide server is to get the tool in the hands of the end user.</p>
<p>The few supporting roles the server has can easily be performed by any other (PHP) server.</p>
<p>So if you like the project but perhaps are mistrusting of servers of others, especially when it comes to keypairs, here's the <a href="https://codeberg.org/yarmo/keyoxide">source code</a> and put it on your own server! Thanks for using the project :)</p>

1
pages/guides/selfhosting-keyoxide.title.html Normal file
View file

@ -0,0 +1 @@
Selfhosting Keyoxide