. // // 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 list the identity proofs stored in our OpenPGP keys.

Listing notations in GnuPG

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

gpg --edit-key FINGERPRINT

List detailed preferences:

showpref

You should now see your key details, uid, and proofs assigned to your keys:


[ultimate] (1). Your Name 
     Cipher: AES256, AES192, AES, 3DES
     Digest: SHA512, SHA384, SHA256, SHA1
     Compression: ZLIB, BZIP2, ZIP, Uncompressed
     Features: MDC, Keyserver no-modify
     Notations: proof@metacode.biz=https://gist.github.com/youruser/somehash
                proof@metacode.biz=dns:yourdomain.org?type=TXT

Exit gpg:

quit