mirror of
https://codeberg.org/keyoxide/keyoxide-web.git
synced 2024-12-22 23:09:29 -07:00
Improve Keybase guide
This commit is contained in:
parent
b2dfd2fbdd
commit
20684fd9c6
1 changed files with 13 additions and 14 deletions
|
@ -2,21 +2,20 @@
|
|||
|
||||
<h3>Claim your Keyoxide profile</h3>
|
||||
|
||||
<p>Have you made your public key accessible through <strong>web key directory</strong> (WKD) on your website or uploaded it to <a href="https://keys.openpgp.org/">keys.openpgp.org</a>? Congratulations, you now have your very own Keyoxide profile!</p>
|
||||
<p>Go to the <a href="/util/profile-url">profile URL generator</a>, set Keybase as Source and follow the Keybase specific instructions. Has a profile URL been generated? Congratulations, you now have your very own Keyoxide profile!</p>
|
||||
|
||||
<h3>Link to your Keyoxide profile</h3>
|
||||
<h3>Actually migrating to Keyoxide</h3>
|
||||
|
||||
<p>
|
||||
Append your OpenPGP key's fingerprint to the domain as such:<br>
|
||||
<strong>https://keyoxide.org/FINGERPRINT</strong><br>and there's your profile page with the public key fetched from <a href="https://keys.openpgp.org/">keys.openpgp.org</a>.
|
||||
</p>
|
||||
<p>Unfortunately, you get very little control when using your Keybase key directly. You will need to generate your own PGP keypair (use guides like <a href="https://spin.atomicobject.com/2013/11/24/secure-gpg-keys-guide/">this one</a> for help) to unlock the full potential of <a href="/guides/proofs">distributed identity proofs</a>.</p>
|
||||
|
||||
<p>
|
||||
If you wish to use WKD instead, simply append your email address as such:<br>
|
||||
<strong>https://keyoxide.org/USER@DOMAIN.ORG</strong>
|
||||
</p>
|
||||
<p>Have you generated a keypair and made the public key accessible through <a href="/guides/web-key-directory">web key directory (WKD)</a> or uploaded it to <a href="https://keys.openpgp.org/">keys.openpgp.org</a>? Use the <a href="/util/profile-url">profile URL generator</a> to get your own profile URL and <a href="/guides">start adding identity proofs</a>.</p>
|
||||
|
||||
<p>
|
||||
Lastly, if you still wish your key to be fetched from <a href="https://keys.openpgp.org/">keys.openpgp.org</a> but using your email address instead of the key's fingerprint, simply override by using the following URL:<br>
|
||||
<strong>https://keyoxide.org/hkp/USER@DOMAIN.ORG</strong>
|
||||
</p>
|
||||
<h3>Keyoxide as a partial replacement for Keybase</h3>
|
||||
|
||||
<p>It's important to moderate expectations and state that <a href="/">Keyoxide</a> only replaces the subset of Keybase features that are considered the "core" features: message encryption, signature verification and identity proofs.</p>
|
||||
|
||||
<p>Message decryption and signing are <strong>not</strong> supported features: they would require you to upload your secret key to a website which is a big <strong>no-no</strong>.</p>
|
||||
|
||||
<p>Encrypted chat and cloud storage are <strong>not</strong> supported features: there are plenty of dedicated alternative services.</p>
|
||||
|
||||
<p>If you need any of these Keybase-specific supports, <a href="/">Keyoxide</a> may not be a full Keybase replacement for you but you could still generate a profile and take advantage of <strong>distributed identity proofs</strong>.</p>
|
||||
|
|
Loading…
Reference in a new issue