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!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
- Merge `sq autocrypt import` has been merged into `sq cert import`.
- Remove `sq autocrypt decode` and `sq autocrypt encode-sender`
without substitute.
- Fixes#187.
- When exporting certificates selected by user IDs (i.e. --email,
--userid, --domain, or --grep), authenticate the bindings and
export only those certificates that can be authenticated.
- Fixes#182.
- The argument `sq network wkd --rsync` which previously had an
optional value argument has been split into two arguments, a
boolean `--rsync` to enable the use of rsync, and `--rsync-path`,
which implies `--rsync`, to specify a path to the local rsync
executable.
- Fixes#370.
- Split authorization functionality out of `sq pki link add` into a
new command, `sq pki link authorize`.
- Align `sq pki link authorize`'s arguments with `sq pki authorize`
arguments.
- Align how user IDs are specified using `sq pki link add` with `sq
pki certify`. Specifically, add a `--add-userid` argument and
remove the `--petname` argument.
- `sq pki link add` has a positional argument for specifying a user
ID directly or by email address. Remove it in favor of the named
arguments, `--userid` and `--email`.
- See #318.
- Previously `sq pki certify` could create certifications, and mark
a certificate as a trusted introducer (when the user set `--depth`
to be greater than zero). Anecdotal evidence indicates that
combining these two actions in a single command is confusing.
- Split the latter functionality off, and put it in a new subcommand,
`sq pki authorize`.
- See https://gitlab.com/sequoia-pgp/sequoia-sq/-/issues/249#note_1865470753
- `sq pki certify` uses a positional argument to specify the
certificate to certify. Change it to be a named argument, either
`--cert`, or `--cert-file`.
- See #318.
- `sq pki certify` uses a positional argument to specify the user
ID to certify. Change it to be a named argument, either
`--userid`, or `--email`.
- This changes the meaning of `--email` from a flag that changes how
`--userid` interprets its argument, to an argument.
- This also allows multiple user IDs to be specified at once.
- See #318.
- Rename `sq network fetch` to `sq network search` to emphasize that
this is key discovery, and may return related or even wrong results.
Likewise for the key server, WKD, and DANE methods.
- See #296.
- By splitting `--handle` into `--cert` and `--key`, where the
former only matches on primary keys, and the latter matches on
both primary keys and subkeys.
- Fixes#287.
- It was possible to use `--allow-not-alive-certifier` and
`--allow-revoked-certifier` to force `sq pki certify` to use
expired and revoked certificates.
- Consistent with the principle that `sq` should support a lot, but
not everything, remove them.
- Fixes#365.
