. // // 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 . ?>

Let's add a decentralized Github proof to your OpenPGP keys.

Post a Github proof message

Name the file openpgp.md and copy the following content into it (make sure to replace FINGERPRINT and USERNAME):

This is an OpenPGP proof that connects [my OpenPGP key](https://keyoxide.org/FINGERPRINT) to [this Github account](https://github.com/USERNAME).
For details check out https://keyoxide.org/guides/openpgp-proofs


[Verifying my OpenPGP key: openpgp4fpr:FINGERPRINT]

After creating a public gist, copy the link to the gist.

Update the PGP key

First, edit the key (make sure to replace FINGERPRINT):

gpg --edit-key FINGERPRINT

Add a new notation:

notation

Enter the notation (make sure to update with the link to the post copied above):

proof@metacode.biz=https://gist.github.com/USERNAME/12345678912345678912345678912345

Save the key:

save

Upload the key to WKD or use the following command to upload the key to keys.openpgp.org (make sure to replace FINGERPRINT):

gpg --keyserver hkps://keys.openpgp.org --send-keys FINGERPRINT

And you're done! Reload your profile page, it should now show a verified Github account.