2020-07-30 04:05:11 -06:00
|
|
|
<!--
|
|
|
|
|
Copyright (C) 2020 Yarmo Mackenbach
|
|
|
|
|
|
|
|
|
|
This program is free software: you can redistribute it and/or modify it under
|
|
|
|
|
the terms of the GNU Affero General Public License as published by the Free
|
|
|
|
|
Software Foundation, either version 3 of the License, or (at your option)
|
|
|
|
|
any later version.
|
|
|
|
|
|
|
|
|
|
This program is distributed in the hope that it will be useful, but WITHOUT
|
|
|
|
|
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
|
|
|
|
|
FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more
|
|
|
|
|
details.
|
|
|
|
|
|
|
|
|
|
You should have received a copy of the GNU Affero General Public License along
|
|
|
|
|
with this program. If not, see <https://www.gnu.org/licenses/>.
|
|
|
|
|
|
|
|
|
|
Also add information on how to contact you by electronic and paper mail.
|
|
|
|
|
|
|
|
|
|
If your software can interact with users remotely through a computer network,
|
|
|
|
|
you should also make sure that it provides a way for users to get its source.
|
|
|
|
|
For example, if your program is a web application, its interface could display
|
|
|
|
|
a "Source" link that leads users to an archive of the code. There are many
|
|
|
|
|
ways you could offer source, and different solutions will be better for different
|
|
|
|
|
programs; see section 13 for the specific requirements.
|
|
|
|
|
|
|
|
|
|
You should also get your employer (if you work as a programmer) or school,
|
|
|
|
|
if any, to sign a "copyright disclaimer" for the program, if necessary. For
|
|
|
|
|
more information on this, and how to apply and follow the GNU AGPL, see <https://www.gnu.org/licenses/>.
|
|
|
|
|
-->
|
2020-06-29 10:02:08 -06:00
|
|
|
<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>
|
