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!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
- Add a header to a list so that it doesn't run into the previous
list. Consider:
```
$ sq network wkd publish --domain example.org /tmp/example.org --cert 9889EAA8B493129489EF7D235CE7215F115DA8A6
Note: Skipping the following certificates because they don't have a valid self-signed user ID in example.org:
- 9889EAA8B493129489EF7D235CE7215F115DA8A6
- F57D5B402CEA11F8F22228A64AC1A5F0C16EE42D
- alice (UNAUTHENTICATED)
- updated
1 update applied.
```
- Hints are printed to `stderr`. If the output is going to `stdout`
and `stdout` is a terminal, first flush `stdout` to reduce the
chance of incorrectly interleaving output and hints.
- Note: this is a precaution; I haven't observed this happen in
practice.
- Change `sq cert list`, `sq pki authenticate`, `sq pki lookup`, `sq
pki identify`, and `sq pki path` to use `stdout`, not `stderr`, for
their main output.
- See #342.
- `print_path_error`, `print_path_header`, `print_path`, and
`ConciseHumanReadableOutputNetwork` unconditionally use `stderr`.
- Change them to take an additional parameter, the stream
to write to.
- This change is in preparation for using these functions to write
to `stdout`.
- See #342.
- `weprintln` and `iweprintln` unconditionally write to `stderr`.
- Change the functions to take an additional parameter, the stream
to write to.
- Rename the functions to `wwriteln` and `iwwriteln` to reflect that
the don't just write to `stderr` anymore, and are now closer to
`writeln`.
- This change is in preparation for using these functions to write
to `stdout`.
- See #342.
- Previously, `sq key list` showed a different error for a certificate
in the certificate store from a certificate that is not in the
certificate store. Align these.
- Fixes#462.
- When `sq inspect` displays a PKESK, it displays the recipient key
ID. For a user of `sq`, this information is nearly useless. The
recipient is normally a subkey, and `sq` doesn't support looking
up certificates by subkey.
- Extend `sq inpsect` to look up the recipient, and display
information about the the associated certificate, if it is
available.
- This adds a mechanism to add a list of certificates presumably
owned by the user to the recipients using the `--for-self` flag.
This makes sure the encrypted message can be decrypted again.
- Fixes#461.
