sshign(1)
π sshign(1) β the manual, but make it make sense
okay so real talk, this is sshign, from section 1 of your General Commands Manual, and it is genuinely one of the cutest little tools ever: it signs stuff and verifies stuff using your SSH keys. no new keypairs, no drama, no "please install a whole PKI bestie" β you literally already have the keys. slay. π
β¨ NAME β¨
sshign β sign and verify data using SSH keys
likeβ¦ that's it. that's the whole vibe. your existing SSH keys, but making promises about data. π
πΈ SYNOPSIS πΈ
sshign secret-key-file < data-to-sign > signature
sshign public-key-file signature-file < data-to-verify
read it like a lil recipe, okay? first form = signing mode (secret key in, signature out). second form = verifying mode (public key + signature in, data on stdin). you got this. π«Ά
π¦ DESCRIPTION π¦
π₯ signing (the "make a signature" era)
To generate a signature, call sshign secret-key-file.
It reads the data from stdin and computes the signature using the private SSH key in secret-key-file, then prints the resulting signature to stdout in text format. text format!! readable!! no weird binary blob situation. iconic behavior, honestly. β¨
π verifying (the "is this legit or nah" era)
To verify a signature, call sshign public-key-file signature-file.
It reads data from stdin and checks the signature in signature-file against the public SSH key in public-key-file.
and here's the part where you pay attention because it's doing numbers:
- returns with exit code
0on successful verification β - returns with exit code
1in case of failed verification β
ngl those exit codes are the whole personality for scripting.0= she ate.1= bestie, that signature did not match. check your exit status, always. π
π EXAMPLES π
signing π
$ echo "This is my message" > sign-me.txt
$ ./sshign ~/.ssh/id_rsa < sign-me.txt > signature.txt
look at that redirect game. data goes in from the file, signature comes out into signature.txt, zero mess. we love a clean pipeline. πΈ
verification π
$ ./sshign ~/.ssh/id_rsa.pub signature.txt < sign-me.txt
verify: ok
and there it is β verify: ok β the four most reassuring characters in this whole manpage. print it, frame it, put it on your fridge. π
π AUTHORS π
Maintained by Thomas Renoth <minus@mnus.de>.
up-to-date sources can be found at https://git.sr.ht/~minus/sshign, and bugs/patches can be submitted by email to ~minus/public-inbox@lists.sr.ht.
so likeβ¦ found a bug? email it. got a patch? email that too. the maintainer literally handed you the inbox. respect the hustle. π
okay that's the whole page bestie, go sign something. π
β this has been the sshign(1) gloss, dated 2026-10-14, straight from the sshign(1) page in your General Commands Manual. no cap, that's the source and version, mwah. π
π¦ where this page comes from
- alpine 3.24: sshign-doc 0.2.1-r44 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms