All zaps are going towards supporting my work on [Indranet](https://github.com/indra-labs/indra)

I know all my posts are signed by my nsec but for proof of me being the main guy building indra, you can check the signatures on the commits under l0k18 and that same public key should be found in the signature at the bottom of this message.

If you ever wanted to know how to use SSH for doing signatures and verifying signatures, I will walk you through it here.

Note that this is a bit clunky because the openssh sign/verify functionality is expecting you to have two files, `filename` and `filename.sig`, which you will see in a lot of places where linux and open source software is available to download. More usually they are gnupg, but if they are ssh this is the way (tm)

my ssh/signing pubkey:

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIB7zKxp+Cr4IxSGhAZDZtY9VJoa/nIMgTWvkhVzd9kSX stalker.loki@protonmail.ch

copy the text until the signature in this post, the last new line included, but none of the rest with the name `text`.

the rest, put into a file `test.sig`

put this content into a file called allowed_signers:

thesigner ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIB7zKxp+Cr4IxSGhAZDZtY9VJoa/nIMgTWvkhVzd9kSX stalker.loki@protonmail.ch

then run this:

cat text | ssh-keygen -Y verify -n nostr -f allowed_signers -s text.sig -I thesigner

and you will get:

Good "nostr" signature for thesigner with ED25519 key SHA256:ljgBk02PEKtWs0FDAMVU0eMpmTAUzk20NzBMr1kyXCU

The `nostr` bit is a "namespace" which acts as an extra mangling that you have to know in order to properly decode the signature and get the key hash.

As you can see I have an `ed25519` key, which is the trendy thing out there in fiat world, but it is possible with gnupg to get `secp256k1` - the bitcoin elliptic curve. Not sure about ssh, as shown above here. ed25519 does have more resistance to signature malleability, I think, but idgaf about fiat curves. lol!

-----BEGIN SSH SIGNATURE-----

U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAgHvMrGn4KvgjFIaEBkNm1j1Umhr

+cgyBNa+SFXN32RJcAAAAFbm9zdHIAAAAAAAAABnNoYTUxMgAAAFMAAAALc3NoLWVkMjU1

MTkAAABA+qPjTPwzgzw9kOPcKsBBSRyXD6OQgvTipUovgwcoQJC38ZnHzv0jfzQylf0pZN

bOZnJ82nEoySPBKsFDCPe/Dw==

-----END SSH SIGNATURE-----