nethsm-random(1)

πŸ“¦ version 0.10.0, in arch rolling

okay bestie, you're looking at nethsm-random(1) from the General Commands Manual β€” the page for the nethsm random command. It's giving secure random bytes with main-character energy, and we're gonna get into every single detail. πŸ’–

🌸 NAME 🌸

nethsm-random β€” the "nethsm random" command, bestie. That's the name, that's the vibe. πŸŽ€

✨ SYNOPSIS ✨

okay so here's the shape of it, literally:

nethsm random [-a|--auth-passphrase-file] [-f|--force] [-c|--config]
       [-o|--output] [-l|--label] [-u|--user] [-h|--help] <LENGTH>

No cap. That's the whole invocation. πŸ’…

πŸ’– DESCRIPTION πŸ’–

girl, the description is short and iconic: this is the "nethsm random" command. That's the official line, and we're not adding lore that isn't there. 😌

πŸ’… OPTIONS πŸ’…

okay bestie, here's every flag and argument β€” no skips, no summarizing, no cap:

  • -a, --auth-passphrase-file <AUTH_PASSPHRASE_FILE> β€” the path to a file containing a passphrase for authentication. The passphrase provided in the file must be the one for the user chosen for the command.

This option can be provided multiple times, which is needed for commands that require multiple roles at once. With multiple passphrase files ordering matters, as the files are assigned to the respective user provided by the --user option. May also be specified with the NETHSM_AUTH_PASSPHRASE_FILE environment variable.

  • -f, --force β€” write to output file even if it exists already. May also be specified with the NETHSM_FORCE environment variable. It's the "yes, write it anyway" button, bestie. ✨
  • -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. So custom config overrides the default spot, periodt. πŸ’…
  • -o, --output <OUTPUT> β€” the optional path to a specific output file. May also be specified with the NETHSM_RANDOM_OUTPUT_FILE environment variable. Optional, but if you want the bytes in a specific file, this is your moment. πŸ¦‹
  • -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. It's the device-picker label, bestie β€” needed when your config has multiple devices. πŸŽ€
  • -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'). Yes, bestie, that's the exact energy: the long help, and the summary lives behind -h. πŸ’€ No extra lore.
  • <LENGTH> β€” the number of random bytes to return. May also be specified with the NETHSM_RANDOM_LENGTH environment variable. This is the argument that tells the command how many random bytes you want. ✨

and that's the page, bestie. Cute sign-off for the footer: it just shows nethsm-random and nethsm-random(1) β€” no source/version or date line in what we were given, so we're not inventing one. Stay random, stay secure, and may your bytes be plentiful. πŸŽ€βœ¨πŸ’–

πŸ“¦ where this page comes from