SQ(1)

πŸ’– SQ-DOWNLOAD β€” the "grab it and make sure it's real" command πŸ’–

okay bestie, imagine this: it's giving manual page, it's giving Sequoia PGP, and it's SQ(1) energy from the very first line. you're in the User Commands section, and this is the glow-up of sq-download. we're downloading stuff, we're checking signatures, we're being so brave about trust. periodt. ✨


🌸 NAME 🌸

sq-download β€” download the data and authenticate it, no cap 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

sq download [OPTIONS]

that's it. that's the whole vibe. sq says "download" and off we go. πŸ’…


✨ DESCRIPTION ✨

bestie. the whole point: Download and authenticate the data. 😌

okay so here's the lore. this command grabs the data from whatever URL you specified, then it checks the signature, and then it authenticates the signer. the way that it does the whole chain… iconic. πŸ”₯

and now the serious part, listen up: if the signer cannot be authenticated, the data is deleted, if possible. not me being dramatic β€” that's literally what it does. vibe check failed means the file gets yeeted. πŸ’€


πŸ‘‘ OPTIONS πŸ‘‘

πŸ’œ Subcommand options πŸ’œ

  • --cleartext β€” verify a cleartext-signed message 🌸
  • --message β€” verify an inline signed message πŸ’Œ
  • --output=FILE β€” write to FILE, or straight to stdout if FILE is literally '-' ✨
  • --signature-url=URL β€” the URL of the signature. use this when the signature is detached from the data, iykyk. and heads up: if no signature is specified, then the signature is assumed to be inline. πŸŽ€
  • --signatures=N β€” set the threshold of valid signatures to N. the way that this works: if this threshold is not reached, the message will not be considered verified. so don't come for her with one lousy signature when you asked for five. πŸ™…β€β™€οΈ default is [default: 1].
  • --signer=FINGERPRINT|KEYID β€” require a signature from a certificate with the specified fingerprint or key ID πŸ”‘
  • --signer-domain=DOMAIN β€” require a signature from a certificate where a user ID includes an email address for the specified domain 🌐
  • --signer-email=EMAIL β€” require a signature from a certificate where a user ID includes the specified email address πŸ“§
  • --signer-file=PATH β€” require a signature from a certificate read from PATH πŸ“
  • --signer-userid=USERID β€” require a signature from a certificate with the specified user ID πŸͺͺ
  • --url=URL β€” the data to download. yes, that's the main character right there. ⭐

🌈 Global options 🌈

See sq(1) for a description of the global options. the lore runs deep, bestie, go read the parent page. πŸ“–


πŸŽ€ EXAMPLES πŸŽ€

download and verify the Debian 12 checksum file β€” here's exactly how, character for character:

sq download --url=file://debian/SHA512SUMS \
       --signature-url=file://debian/SHA512SUMS.sign \
       --signer=DF9B9C49EAA9298432589D76DA87E80D6294BE9B \
       --output=SHA512SUMS

not me putting the entire fingerprint in there. DF9B9C49EAA9298432589D76DA87E80D6294BE9B ate and left no crumbs. πŸ’…


πŸ¦„ SEE ALSO πŸ¦„


πŸ“ VERSION πŸ“

1.5.0 β€” that's the one, babe.


and that's the whole page, bestie!! go download something and authenticate it responsibly. mwah. πŸ«ΆπŸ’–

signed off with love by Sequoia PGP, version 1.5.0, page SQ(1), section 1 β€” stay iconic, stay verified. βœ¨πŸ‘‘

πŸ“¦ where this page comes from