mu-verify1
Verify message signatures and display information about them
Usage
mu [COMMON-OPTIONS]
verify
[OPTIONS]
[FILE ...]
Overview
mu verify is the mu command for verifying message signatures (such as PGP/GPG signatures) and displaying information about them. The sub-command works on message files, and does not require the message to be indexed in the database.
If no message file is provided, the command expects the message on standard-input.
Options
-r, --auto-retrieve
Attempt to find keys online (see the auto-key-retrieve option in the gnupg(1) documentation).
--decrypt
Attempt to decrypt the message.
Options
-d, --debug
Makes mu generate extra debug information, useful for debugging the program itself. Debug information goes to the standard logging location; see mu(1).
-q, --quiet
Causes mu not to output informational messages and progress information to standard output, but only to the log file. Error messages will still be sent to standard error. Note that mu index is much faster with --quiet, so it is recommended you use this option when using mu from scripts etc.
--log-stderr
Causes mu to not output log messages to standard error, in addition to sending them to the standard logging location.
--nocolor
Do not use ANSI colors. The environment variable NO_COLOR can be used as an alternative to --nocolor.
-V, --version
Prints mu version and copyright information.
-h, --help
Lists the various command line options.
Examples
To display aggregated (one-line) information about the verification status in a message:
$ mu verify msgfile
To display information about all the signatures:
$ mu verify --verbose msgfile
If you only want to use the exit code, you can use:
$ mu verify --quiet msgfile
which does not give any output unless there is an error.
History
- Debian 13 (Trixie): the text shown here
- Debian 12 (Bookworm)
- Debian 11 (Bullseye)
- Debian 10 (Buster) to Debian 9 (Stretch)
- Debian 8 (Jessie)
--auto-retrieve until Debian 12 (Bookworm);
-r until Debian 12 (Bookworm).