Orcmid's Identifier on GitHub and elsewhere

keybase.md

Keybase proof

I hereby claim:

• I am orcmid on github.
• I am orcmid (https://keybase.io/orcmid) on keybase.
• I have a public key whose fingerprint is 04D0 4322 979B 84DE 1077 0334 F96E 89FF D456 628A

To claim this, I am signing this object:

{
    "body": {
        "key": {
            "fingerprint": "04d04322979b84de10770334f96e89ffd456628a",
            "host": "keybase.io",
            "key_id": "F96E89FFD456628A",
            "uid": "330ce16c71a34cbfce611bb6459f4a00",
            "username": "orcmid"
        },
        "service": {
            "name": "github",
            "username": "orcmid"
        },
        "type": "web_service_binding",
        "version": 1
    },
    "ctime": 1397348809,
    "expire_in": 157680000,
    "prev": "9128924392520655abf55bea97185361bebdea15e6729d45b2f948aea1ec6162",
    "seqno": 7,
    "tag": "signature"
}

with the PGP key whose fingerprint is 04D0 4322 979B 84DE 1077 0334 F96E 89FF D456 628A (captured above as body.key.fingerprint), yielding the PGP signature:

-----BEGIN PGP MESSAGE-----
Version: GnuPG v2.0.22 (MingW32)

owF1kWtIFFEYhnfUriZ2hdAyOUaFbTb3yyK0oWklVFAZprXMmTmzDuLsOrtrmVis
GK4ZpZCkSSGF4SYYBRYSqeCPbNOIKCTdSoMuPyTL6EZInTH72flzOO/3vC/fd76G
hFhbDPHTqPv9LB+eIR71v4O2/btejFUC6FErgKMSlKDZS9MNNzK9pm74gQOQrEqy
DE1LggRFVkUUKQgkw7CaxCNR0jSV5XieFmVgB8Uen+XAMVD2oQzdgzX8cOkqVnMk
foco5eRk/+W341pgtsAwpIIoXhEomWEVqCmIpygIeZaTNFYmSQv0IdOQSxGmPaZS
im1VdoC1cl1BVsdzNbfuLw7A//H+Cq8lHEPQNWd1Qd1Q8bDYUY5Mn+4xgIPCpOLX
LS/FSALDiiIp2QE67tVN5NItghN4kcTHDrwmKseREkWLEs0yEs3RJM9xMtQ4DiJZ
EiiRY3gKIqgimeIQL9AS/i9IaxIrylhCCk/xNLCGKTM8wCHgNmU3jvTpbkP2B0wE
quqINXE2IsY2f16MtS7b4kVL/y2R/LXQdnXnRF/4XMZAwpH0XWejkeps9U5K9/SD
rJ60nv7sxotvo9HE1C+jkdOhyoLUoY6ESC1aee92S33NU7O1rWX8/MvvR4MCoaJt
Lvelhs6ZpEDZUGaX88lUAVn7cPdo/550uCp38FDhiNO1YHxTtJ14Mxm7jI6bbpxo
iPYNt15fX5i5YbLoeQdxYQnb1vTt1d2s6cPBmxtv7Q3XsHn575dPbDmxdV3v5rGu
XrX+8YePtYOvP8cX2pszum9ErnVWJ3+diVw5mRe974tvXqvDkX0/mtRgWsqB3vZQ
KCnZWZQ5EIzT6OFToUk9XDAVHrGvKAGfEnMdqro6rdUZSb18sI/9Aw==
=5Amg
-----END PGP MESSAGE-----

And finally, I am proving ownership of the github account by posting this as a gist.

My publicly-auditable identity:

https://keybase.io/orcmid

From the command line:

Consider the keybase command line program.

# look me up
keybase id orcmid

# encrypt a message to me
keybase encrypt orcmid -m 'a secret message...'

# ...and more...

How can you verify this proof yourself?

Browsing at this gist page, select "View Raw" (the "<>" button at the top of the display of this text).

When you see the plain-text version, select and copy to your clip-board just the lines starting with "-----BEGIN PGP MESSAGE----" and ending with "-----END PGP MESSAGE-----".

Save the extraction into a text file and save it with a name ending in .asc (Say, orcmid-keybase-gist.json.asc). Put it in a directory where it is easy for you to find from the command line. A download directory is often a good choice.

Verify that the BEGIN and END messages are on lines by themselves and the starting "-----" are at the beginning of those lines with nothing in front of them.

Obtain a copy of the public key with the fingerprint identified above. You can obtain it at the http://keybase.io/orcmid page. You can also obtain it using the ">keybase id orcmid" command from the command line.

Now use GnuPG to both extract the signed text and verify the signature. Open a command-line console, the same one that you can use keybase from. Navigate to the folder where you stored the .asc file. Then perform a gpg command where the only parameter is the name of that file. For example,

>gpg orcmid-keybase-gist.json.asc

GnuPG will recognize that that is an ASCII-armored signed file. It will attempt to verify the signature and it will respond with a report on the success or failure of the verification.

In addition, gpg will extract the signed material in the same location as the .asc file. It will have the same name except the ".asc" portion is removed.

Open the extracted file in a text editor (or a JSON editor if you have one of those). If you look at the raw text, you will see that it is exactly the same as the JSON text on this page except there are no spaces or line breaks. It is a tight version of the same text.

That's essentially what it takes.

Note that you do not need keybase installed to verify this page. You can obtain my keybase.io/orcmid public key with that fingerprint from a PGP key server directly using a PGP or GnuPG application. Or you can download the ASCII-armored text file at https://keybase.io/orcmid/key.asc and save it as a .asc file on your computer. Don't view it and save it. That will produce an HTML file. Instead, on the Orcmid's Public Key pop-up, download the link given on the "curl/raw:" line. Be sure to change the name to one ending in .asc, such as orcmid-keybase-key.asc. Then, using a console session as above, if you use the command

>gpg orcmid-keybase-key.asc

GPG will describe the key to you.

You can install it using

>gpg --import orcmid-keybase-key.asc

This is now usable in verifying signatures and also encrypting material that can be decrypted only by someone having the use of the private key that corresponds to this public key.