keybase.io

keybase.md

Keybase proof

I hereby claim:

• I am hilbix on github.
• I am hilbix (https://keybase.io/hilbix) on keybase.
• I have a public key ASCx_F6R2C8_UowExr0c1ZZ6Fp37u8N3Jb0EjAoUWYNoUQo

To claim this, I am signing this object:

{
  "body": {
    "key": {
      "eldest_kid": "0120b1fc5e91d82f3f528c04c6bd1cd5967a169dfbbbc37725bd048c0a14598368510a",
      "host": "keybase.io",
      "kid": "0120b1fc5e91d82f3f528c04c6bd1cd5967a169dfbbbc37725bd048c0a14598368510a",
      "uid": "abd0303ec5f27115fff1aaaee6f34419",
      "username": "hilbix"
    },
    "merkle_root": {
      "ctime": 1602514273,
      "hash": "a043d8a85d5eb081c5ea7e8295db267e29f508896348642cc240953db1521f5a1fb9646d04f8319a5bedb8c212fa7ff4cbd80268174b28aac6f4171fb37fd8af",
      "hash_meta": "6295e6d419e8e72bf2e5ed93972b0427ec946f4c9728aaf65052af795b2b4bd1",
      "seqno": 17807953
    },
    "service": {
      "entropy": "NNM34A9WmxdAyopYboaSceX0",
      "name": "github",
      "username": "hilbix"
    },
    "type": "web_service_binding",
    "version": 2
  },
  "client": {
    "name": "keybase.io go client",
    "version": "5.5.0"
  },
  "ctime": 1602514317,
  "expire_in": 504576000,
  "prev": "ab21e992e25ac93a91c9caf0dd6791f5f05201078176ea27fbfa7b42f3cc2010",
  "seqno": 4,
  "tag": "signature"
}

with the key ASCx_F6R2C8_UowExr0c1ZZ6Fp37u8N3Jb0EjAoUWYNoUQo, yielding the signature:

hKRib2R5hqhkZXRhY2hlZMOpaGFzaF90eXBlCqNrZXnEIwEgsfxekdgvP1KMBMa9HNWWehad+7vDdyW9BIwKFFmDaFEKp3BheWxvYWTESpcCBMQgqyHpkuJayTqRycrw3WeR9fBSAQeBduon+/p7QvPMIBDEIFVLlUy+ntW+94EnjlBRmZ4eIfJMG+G2zWedkzJdnFc+AgHCo3NpZ8RAbO8JBAsph/UFTA82XIE+DcLf9NshedARP8ULyiUXaCiblOVia/fujQcv48cJj7miJy+Jlp+tVP+/Fr2KVVw3B6hzaWdfdHlwZSCkaGFzaIKkdHlwZQildmFsdWXEIE0510n0BJ4Qp5e1XUDmv/crcLAOiSgsqkiHARdbnH8no3RhZ80CAqd2ZXJzaW9uAQ==

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

My publicly-auditable identity:

https://keybase.io/hilbix

From the command line:

Consider the keybase command line program.

# look me up
keybase id hilbix

Last try: In the gists of others there is an empty line after the sig. Perhaps .. let's see.

Nope, no avail.

BTW what does this mean: "verifyable by keybase or clinacl"? For whom? Cipherpunks?

Where are the instructions, the example on how to do this verification. Then one (perhaps) can find out what's wrong and fix it.

But without .. nothing .. completely lost. (BTW: I probably know how to find out how to verify. But first I have to setup a scratch machine, because neither keybase nor clinacl are available from any approved Debian repository - and by security policy third party software must not be installed on my machines, either it's officially from the OS vendor or from some few trusted parties -. But this is not the point. The point is, that the whole thing is far too complex and lacking in-detail step-by-step instructions on how to archive the desired goal, combined with some real useful diagnostic information.)

All what I see is "unavailable". Unavailable .. what? GitHub? Internet? Brain?

Every Verification is sacred
Every Verification is good
Every Verification is needed
In your neighbourhood!

Read: Something went terribly wrong as I apparently pasted the wrong thing. Why? Could it possibly mean there is lacking some documentation? Perhaps?

Yehaw! The original text is available. Not for humans. But for something like my shell tool json2sh:

eval "$(curl 'https://keybase.io/_/api/1.0/sig/get.json?sig_id=8144468e5faf192fe05c3dca4b36124ccdd1a577f4be702ee9de16cc3b071d7f0f' | json2sh)";
printf '%s' "$JSON__0_sigs_1_proof__text__full" | xclip -i

Let's see what this gives then.

Nope, just minimum difference on the last line, and still does not work.

Some days later I got the mail that it now worked. Wohoo!

I really do not understand. It is as it is.