1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
|
use clap::Parser;
use super::IoArgs;
#[derive(Parser, Debug)]
#[clap(
name = "verify",
about = "Verifies signed messages or detached signatures",
long_about = "Verifies signed messages or detached signatures
When verifying signed messages, the message is written to stdout or
the file given to --output.
When a detached message is verified, no output is produced. Detached
signatures are often used to sign software packages.
Verification is only successful if there is no bad signature, and the
number of successfully verified signatures reaches the threshold
configured with the \"--signatures\" parameter. If the verification
fails, the program terminates with an exit status indicating failure.
In addition to that, the last 25 MiB of the message are withheld,
i.e. if the message is smaller than 25 MiB, no output is produced, and
if it is larger, then the output will be truncated.
The converse operation is \"sq sign\".
",
after_help =
"EXAMPLES:
# Verify a signed message
$ sq verify --signer-cert juliet.pgp signed-message.pgp
# Verify a detached message
$ sq verify --signer-cert juliet.pgp --detached message.sig message.txt
SEE ALSO:
If you are looking for a standalone program to verify detached
signatures, consider using sequoia-sqv.
",
)]
pub struct Command {
#[clap(flatten)]
pub io: IoArgs,
#[clap(
long = "detached",
value_name = "SIG",
help = "Verifies a detached signature"
)]
pub detached: Option<String>,
#[clap(
short = 'n',
long = "signatures",
value_name = "N",
default_value_t = 1,
help = "Sets the threshold of valid signatures to N",
long_help = "Sets the threshold of valid signatures to N. \
If this threshold is not reached, the message \
will not be considered verified."
)]
pub signatures: usize,
#[clap(
long = "signer-cert",
value_name = "CERT",
help = "Verifies signatures with CERT",
)]
// TODO: Should at least one sender_cert_file be required? Verification does not make sense
// without one, does it?
// TODO Use PathBuf instead of String. Path representation is platform dependent, so Rust's
// utf-8 Strings are not quite appropriate.
// TODO: And adapt load_certs in sq.rs
pub sender_cert_file: Vec<String>,
}
|
