Mirrors/keyoxide-web
1
0
Fork 1
mirror of https://codeberg.org/keyoxide/keyoxide-web.git synced 2024-12-22 23:09:29 -07:00
Code Issues Projects Releases Packages Wiki Activity

Add guide

Browse source
This commit is contained in:
Yarmo Mackenbach 2020-06-29 01:15:43 +02:00
parent cab28d4b7a
commit 988f0e70c9
3 changed files with 35 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
pages/guides.html
View file

@ -25,6 +25,7 @@
<div class="content"> <div class="content">
<h3>Using keyoxide.org</h3> <h3>Using keyoxide.org</h3>
<a href="/guides/migrating-from-keybase">Migrating from Keybase</a><br> <a href="/guides/migrating-from-keybase">Migrating from Keybase</a><br>
<a href="/guides/feature-comparison-keybase">Feature comparison with Keybase</a><br>
<h3>Adding proofs</h3> <h3>Adding proofs</h3>
<a href="/guides/dns">Adding a DNS proof</a><br> <a href="/guides/dns">Adding a DNS proof</a><br>

33
pages/guides/feature-comparison-keybase.content.html Normal file
View file

@ -0,0 +1,33 @@
<p>Let's see how Keyoxide's features compare to those of Keybase.</p>
<h3>Encrypt and verify</h3>
<p>Both Keyoxide and Keybase allow easy encryption of data and verification of signatures. While Keybase can only perform these actions for their users, Keyoxide can do this for any key key on the internet, whether it's available through web key directory, dedicated key servers or simply copy-pasting a plaintext key.</p>
<h3>Decrypt and sign</h3>
<p>Keyoxide cannot decrypt data or sign messages.</p>
<p>Keybase can do both of those things but this should NOT be considered a feature. It requires one to upload their private key to closed-source servers which is an act in stark contradiction with all safety precautions any owner of a private key should aim to heed.</p>
<h3>Online identity proofs</h3>
<p>Both Keyoxide and Keybase allow the user to generate proofs of online identity on various platforms. The difference lies in the method of generation and the implications this has on security.</p>
<p>Keybase generates a signed message to be posted by the to-be-verified account. Since this involves a signature, any signing key can be used. If a signing key gets misappropriated, it becomes easy for a bad actor to create fake identity proofs.</p>
<p>Keyoxide uses decentralized OpenPGP proofs in which the identity proofs are stored as notations within the keys themselves. This is only possible when you have access to keys with "certification" capability. As these are the most valuable of keys, they should also be handled more securely than signing keys and are therefore less prone to forgery of identity proofs.</p>
<h3>Social network and additional services</h3>
<p>Keybase provides an additional social network, chat functionality, encrypted drive, encrypted git, XLM crypto wallet and much more.</p>
<p>Keyoxide has none of that. Just keys and proofs.</p>
<h3>Openness</h3>
<p>Keyoxide is fully open-source. It consists mainly of a client component which is the browser. The supporting server functions are open-source as well.</p>
<p>Keybase has open-source clients but closed-source servers.</p>
<h3>Data safety</h3>
<p>Keyoxide lets the user's devices do almost all of the heavy lifting, meaning no data is ever sent to a server to perform any of the actions. Only exceptions to this rule are a couple of "proxy scripts" for proofs that cannot be verified by a browser. These proxy scripts are open-source as well and inspectable by all.</p>
<p>Keybase servers are closed-source. One does not know what happens inside that black box.</p>

1
pages/guides/feature-comparison-keybase.title.html Normal file
View file

@ -0,0 +1 @@
Feature comparison with Keybase