IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
- Change `sq key revoke`, `sq key subkey revoke`, and `sq key userid
revoke` to support the cert store and key store.
- Add `--cert` to specify a certificate by key ID or fingerprint.
- If `--output` is not specified and `--cert` is, import the
modified certificate into the cert store. If `--output` is not
specified and `--cert-file` is, write the modified certificate to
stdout.
- Change the `--cert-file` and `--revoker-file` arguments to `sq key
revoked`, `sq key userid revoke`, and `sq key subkey revoke` to
interpret `-` as meaning reading from stdin.
- `sq key revoked`, `sq key userid revoke`, and `sq key subkey
revoke` have two arguments for naming a certificate:
`--certificate-file` and `--cert-file`. The latter is an alias.
Drop `--certificate-file` and promote `--cert-file`. This
harmonizes these subcommands with other subcommands, which only
use `--cert-file`.
- Rename `--revocation-file` to `--revoker-file`, as the file
contains a "revoker" not a "revocation."
- The implementations of `RevocationOutput::write` are nearly
identical.
- Refactor `RevocationOutput` to provide a default implementation of
the `write` method.
- Change `sq key userid add` to support the cert store and key
store.
- Add `--cert` to specify a certificate by key ID or fingerprint.
- Change the positional file argument to `--cert-file`.
- Change the positional user ID to `--userid`.
- If `--output` is not specified and `--cert` is, import the
modified certificate into the cert store. If `--output` is not
specified and `--cert-file` is, write the modified certificate to
stdout
- Improve the documentation for `Sq::get_keys`,
`Sq::get_primary_keys`, `Sq::get_primary_key`,
`Sq::get_signing_keys`, `Sq::get_signing_key`,
`Sq::get_certification_keys`, and `Sq::get_certification_key`.
- Add `Sq::get_certification_key`, which is a wrapper around
`Sq::get_certification_keys`, for the case where only one
certificate is looked up.
- Update users.
- Make the functions `get_keys`, `get_primary_keys`,
`get_signing_keys` and `get_certification_keys` methods on `Sq`.
- Move the associated types, `GetKeysOptions`, and `KeyType`, to the
`sq` module.
- Change `sign`, `sign_data`, `sign_message`, `sign_message_` and
`clearsign` to not have their own `time` parameters, but to use `Sq`
for their configuration.
- When generating a new key, and saving that key to the key store,
don't require that the user think about where the revocation
certificate should be saved; just save it in the Sequoia home
directory.
- Use `sequoia-directories` to compute the home directory, and the
various component directories.
- This also allows the use of `SEQUOIA_HOME` to set the home
directory.
- While the commit b5a7d15710 moved the
"sq link" command under "sq pki", there are some left-overs in the
error messages.
Signed-off-by: Daiki Ueno <dueno@redhat.com>
- Change `sq pki list`, etc. to work with subkey key IDs and
fingerprints.
- Consider: a user examines a signature using `sq inspect,, and then
looks up the signer's key ID. We shouldn't say that the
certificate is not found, but allow naming the certificate by the
subkey's key ID.
- Fixes#246.
- When `sq inspect` shows an `Alleged signer` or an `Alleged
certifier`, it only shows the signing key's key ID. Use
`best_effort_primary_uid_for` to also display a label.
- Fixes#242.
- The output of `sq pki list`, `sq pki authenticate`, `sq pki
identify` and `sq pki lookup` are overwhelming.
- Change the output to only show whether a binding can be
authenticated, not the paths; group the user IDs according
to the certificate; and, show whether the components are expired
or revoked.
- Use the old output format if the user passes `--show-paths`.
- Fixes#240.
- When `sq decrypt` prompts for a password to decrypt the PKESK,
don't just show the recipient's key ID, also show the
certificate's user ID, if that is available.
- If decrypting a message fails, show the message's recipients.
This may help the user debug the problem, e.g., it is not
encrypted to them, or they need to import a key.
- Fixes#231.
