Age | Commit message (Collapse) | Author |
|
- https://rust-lang.github.io/rust-clippy/master/index.html#needless_return
|
|
- https://rust-lang.github.io/rust-clippy/master/index.html#match_like_matches_macro
|
|
- https://rust-lang.github.io/rust-clippy/master/index.html#redundant_closure
|
|
- https://rust-lang.github.io/rust-clippy/master/index.html#useless_conversion
|
|
- https://rust-lang.github.io/rust-clippy/master/index.html#or_fun_call
|
|
- Compiling with 1.51 toolchains prints warnings about redundant
semicolons. Remove them.
|
|
|
|
- Try hard to list the most relevant (i.e. primary) user id.
- Add a flag --all-userids to list all userids.
|
|
- Fixes #689.
|
|
- Fixes #690.
|
|
- Fixes 1eee13d7035718eddc1163d7e0432299aee15ffe.
|
|
|
|
- We now explain the errors like sequoia-sop:
% sq verify --detached msg.sig --signer-cert ... < msg
Error verifying checksum from 39D100AB67D5BD8C04010205FB3751F1587DAEF1:
Policy rejected non-revocation signature (Binary) requiring collision resistance
because: MD5 is not considered secure since 1997-02-01T00:00:00Z
1 bad checksum.
Error: Verification failed
- Fixes #676.
|
|
This reverts commit 6e555106da58e943a7f2a3091c89c282232fc968.
|
|
- Only emit the warning if we detect non-interactive use and are
emitting data that could be scraped resulting in fragile
constructs.
- Fixes #653.
|
|
- Make the create_or_stdout* functions available as methods on the
Config struct. Adapt callsites.
- Also, differentiate between data that is safe to redirect to a
file or pipe to the next program (e.g. OpenPGP data, decrypted or
authenticated payloads) and data that could possibly be
scraped (e.g. packet dumps).
|
|
|
|
- Require at least one valid signature for `sq verify`. For `sq
decrypt`, require one if at least one signer cert is given.
- Document what happens if signature verification fails, or message
tampering is detected using the SEIP packet.
- Fixes #677.
|
|
- Fixes #273.
|
|
- Add 'Note:' and fix alignment.
|
|
- The conditional was inverted by mistake.
- Fixes 4df9befdb10cc336a9df49b65fdfef659296aa61.
- Fixes #662.
|
|
- See #677.
|
|
- See #151.
|
|
|
|
|
|
- Fixes #383.
|
|
|
|
|
|
- Add a simple heuristic for bash.
- See #653.
|
|
The synopsis clearly places TARGET-KEY *after* the options. But the
example places it haphazardly within the options, which is harder to
read and understand.
Even if the original example works, the goal of the example should be
to make it easy to see what is happening in a standard usage, not to
show off the flexibility of the parser.
|
|
- Fixes #652.
|
|
- Fixes #655.
|
|
- We generate manpages from the cli definition. It turns out that '
is special character in troff, and the man crate doesn't take care
of escaping it correctly. As a pragmatic workaround, switch to "
instead.
|
|
|
|
|
|
- This will help in generating manpages for all combination of
features.
|
|
- DRY.
- Using serialize_keyring has the advantage that it also outputs
descriptive ascii-armor headers.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Add an option to convert any keys in the input to certificates.
- This removes any secret key material thereby turning a key into a
certificate.
|
|
- All of the 'sq certring' operations apply equally well to
'keyrings'.
- Consistent with the new name, don't strip secret key material.
|
|
- Add the `--notation` option to `sq sign` and `sq certify` to add
notations to the generated signature.
|
|
|
|
|
|
- This works around the bug fixed in
acbcd3360bdc0091769d2367c7bd97363b8aa087 and thus fixes armor
detection when compiled using buffered-reader 1.0.0.
|
|
|