nethsm-key-decrypt(1)

πŸ“¦ version 0.10.0, in arch rolling

πŸ’… nethsm-key-decrypt(1) πŸ’…

okay bestie, welcome to nethsm-key-decrypt(1) from the General Commands Manual β€” this is the page for the nethsm key decrypt command, and we’re gonna make it make sense. no cap. 🫢✨


✨ NAME ✨

nethsm-key-decrypt β€” the nethsm key decrypt command. that’s the name, that’s the vibe. πŸ’–

🌸 SYNOPSIS 🌸

nethsm key decrypt [-a|--auth-passphrase-file] [-f|--force]
[-c|--config] [-i|--initialization-vector] [-l|--label] [-o|--output]
[-u|--user] [-h|--help] <KEY_ID> <MESSAGE> [DECRYPT_MODE]

πŸ’– DESCRIPTION πŸ’–

this page is literally all about the nethsm key decrypt command. that’s the description, periodt. ✨

πŸŽ€ OPTIONS πŸŽ€

  • -a, --auth-passphrase-file <AUTH_PASSPHRASE_FILE> β€” this is the path to a file that holds a passphrase for authentication. the passphrase inside has to be the one for the user you chose for the command. you can pass this option multiple times, which is needed for commands that require multiple roles at once. with multiple passphrase files, ordering matters, because the files get assigned to the respective user from the --user option. may also be specified with the NETHSM_AUTH_PASSPHRASE_FILE environment variable. πŸ”
  • -f, --force β€” write to the output file even if it exists already. may also be specified with the NETHSM_FORCE environment variable. πŸ’₯
  • -c, --config <CONFIG> β€” the path to a custom configuration file. if specified, the custom configuration file is used instead of the default configuration file location. may also be specified with the NETHSM_CONFIG environment variable. πŸ—‚οΈ
  • -i, --initialization-vector <INITIALIZATION_VECTOR> β€” the path to a file containing the initialization vector (IV) for symmetric decryption. heads up: the IV can only be used when choosing symmetric decryption (i.e. with AesCbc). may also be specified with the NETHSM_KEY_DECRYPT_IV environment variable. 🧚
  • -l, --label <LABEL> β€” a label uniquely identifying a device in the configuration file. must be provided if more than one device is setup in the configuration file. may also be specified with the NETHSM_LABEL environment variable. 🏷️
  • -o, --output <OUTPUT> β€” the path to a specific file to write the decrypted message to. may also be specified with the NETHSM_KEY_DECRYPT_OUTPUT environment variable. πŸ“
  • -u, --user <USER> β€” a user name which is used for a command. can be provided if no user name is setup in the configuration file for a device. must be provided if several user names of the same target role are setup in the configuration file for a device. this option can be provided multiple times, which is needed for commands that require multiple roles at once. may also be specified with the NETHSM_USER environment variable. πŸ‘‘
  • -h, --help β€” print help (see a summary with -h). iykyk, bestie. 🫢
  • <KEY_ID> β€” the ID of the key to use for decryption. may also be specified with the NETHSM_KEY_ID environment variable. πŸ”‘
  • <MESSAGE> β€” the path to an encrypted message to decrypt. may also be specified with the NETHSM_KEY_DECRYPT_MESSAGE environment variable. πŸ’Œ
  • [DECRYPT_MODE] β€” the decryption mode to use. one of ["AesCbc", "OaepMd5", "OaepSha1", "OaepSha224", "OaepSha256", "OaepSha384", "OaepSha512", "Pkcs1", "Raw"] (defaults to "Raw"). may also be specified with the NETHSM_KEY_DECRYPT_MODE environment variable. 🌈

kisses, bestie β€” this footer sign-off is brought to you by source/version nethsm-key-decrypt and page label nethsm-key-decrypt(1), and there’s no date on the footer, so I’m not inventing one. fr fr. πŸ«ΆπŸ’…

πŸ“¦ where this page comes from