LSH-DECRYPT-KEY(1)

💅 LSH-DECRYPT-KEY 💅

okay bestie, welcome to the lsh manual pages, specifically the one for lsh-decrypt-key — it lives in the Lsh Manuals section (section 1, the user commands girlies) 🎀

---

✨ NAME ✨

lsh-decrypt-key — Decrypts the given key and outputs it in unecrypted form.

(no i did not typo that, the original says "unecrypted", we respect the ancestors 💀)

---

🌸 SYNOPSIS 🌸

lsh-decrypt-key [OPTION...]

---

🦋 DESCRIPTION 🦋

CAUTION! The information in this manpage may be invalid or outdated. For authorative information on lsh, please see it's Texinfo manual (see the SEE ALSO section).

okay so real talk, this page might be giving 2004 energy and possibly stale info, so for the actually-authoritative lore you gotta hit the Texinfo manual. iykyk 💅

So here's the vibe: the given key (supplied on stdin or in the file given with the --in option) and it's passphrase is read. The key is decrypted and written to stdout (or the file supplied by the --out option).

This program is usually invoked by the lsh-upgrade-key script. she's a supporting character, not the main character, and that's fine 🌈

---

✨ OPTIONS ✨

• --askpass=Program — the Program you wanna use for reading passwords. Should be an absolute filename. like, absolutely absolute, no vibes-based relative paths 🫶
• --in=encrypted key filename — where the encrypted key is coming from. (defaults to stdin)
• --out=decrypted key filename — where the decrypted key goes. (defaults to stdout)
• --debug — Print huge amounts of debug information. like HUGE. it's giving firehose 🚿
• --log-file=File name — Append messages to this file. yes, append, she adds to the end, she does not overwrite 👑
• -q, --quiet — Suppress all warnings and diagnostic messages. shhh. no thoughts, no warnings, just vibes 🤫
• --trace — Detailed trace. even more detailed than debug apparently. the way that this exists separately from --debug… iconic 🔥
• -v, --verbose — Verbose diagnostic messages.
• -?, --help — Give this help list. yes the flag is literally a question mark, she's quirky like that 😭
• --usage — Give a short usage message. the tl;dr version 💀
• -V, --version — Print program version. tell me who you are bestie 🌸

---

💜 DIAGNOSTICS 💜

See the --verbose , --trace and --debug options. those three are the gossip channels, pick your volume 📢

---

🍓 REPORTING BUGS 🍓

Report bugs to <bug-lsh@gnu.org>.

(be nice, be specific, include the receipts 🧾)

---

👑 COPYING 👑

The lsh suite of programs is distributed under the GNU General Public License; see the COPYING and AUTHORS files in the source distribution for details. fr fr, go read them, they're right there 💖

---

🎀 AUTHOR 🎀

The lsh program suite is written mainly by Niels Möller <nisse@lysator.liu.se>. legend behavior, no cap 🌟

This man-page was written for lsh 2.0 by Pontus Freyhult <pont_lsh@soua.net>, it is based on a template written by J.H.M. Dassen (Ray) <jdassen@wi.LeidenUniv.nl>. shoutout to the template girlies too 🫶

---

🌈 SEE ALSO 🌈

DSA(5), lsh(1), lsh-authorize(1), lsh-decode-key(1), lsh-export-key(1), lsh-keygen(1), lsh-make-seed(1), lsh-upgrade(1), lsh-upgrade-key(1), lsh-writekey(1), lshd(8), secsh(5), SHA(5), SPKI(5), ssh-conv(1)

The full documentation for lsh is maintained as a Texinfo manual. If the info and lsh programs are properly installed at your site, the command

info lsh

should give you access to the complete manual. go drink from the source bestie 💧✨

---

and that's the whole page, babes 🦋 this one's from NOVEMBER 2004 and it's part of the lsh 2.0 era — stay gorgeous, stay decrypted, and remember: lsh-decrypt-key said what she said 💅💖