Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
This reverts commit d87c4b60c4946fbc7ccb8c0faa4609fffbb05a23.
|
|
|
|
This reverts commit 106be48debc8461e6d033a630838936817d9b446.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Fixes https://gitlab.com/sequoia-pgp/sequoia-sq/-/issues/88
|
|
- We may not understand all of the certs, but that is no reason not
to return them.
|
|
|
|
- Change both functions to return a vector of Result<Cert>. First,
the keyserver may return more than one cert for both user ID
searches as well as searches by key handle. Second, we may
understand not all certs returned by the server, and that is okay,
and we shouldn't let the whole query fail because of that.
- Previously, the functions made an attempt at validating the
results. However, that is flawed. First, in the case of
retrieval by key handle, the test was brittle and easily
circumvented by a key server. Second, the server may have good
reason to return an additional cert, even if it doesn't have the
key handle that the user asked for. For example, it may know that
a cert is superseded and return the new one too, as a courtesy.
draft-shaw-openpgp-hkp-00 doesn't forbid that.
- In the case of search by email address, the server may know the
association between the queried email address and the cert, even
if said association is not recorded in the cert itself.
- Remove the brittle checks, return all certs returned by the
server, add a warning to the documentation of KeyServer::get.
|
|
|
|
- We may not understand all of the returned certs, and that is
okay. Change the return type to reflect that.
- Also, one resource record may only contain one cert. Adapt
accordingly.
|
|
- This is likely an oversight in the original commit, as it wasn't
mentioned in the commit message. We don't have such an interface
for wkd or hkp either.
|
|
- As we use types from reqwest in our API, re-export it as a
courtesy for downstream consumers. This way, they can use the
re-exported reqwest and be confident that they use the correct
version.
|
|
- Fixes #840.
|
|
- This was duplicated by accident in
bc1f27770002690f6117eaec59e8b11ca6196489.
|
|
- Fixes #878.
|
|
- This is safe, as it is not possible to change the shape of the
data through a mutable reference (e.g. it is not possible to take
the secret key material away).
|
|
- Fixes #980.
|
|
in version 1.17.0 of sequoia-openpgp
|
|
- Fixes #1062.
|
|
|
|
- Tests that an inline-signed message using two different hash
algorithms verifies correctly.
|
|
|
|
- This triggers a warning in rustc 1.73, and thus is an error for
us.
|
|
|
|
- Fixes #1063.
|
|
|
|
|
|
|
|
|
|
- Upgrade clap from clap 3 to clap 4.
- Use the opportunity to change to clap's derive-style API.
|
|
|
|
|
|
- We've configured the gitlab project so that the only way to push
to main is via a merge request for which CI has passed. As such,
running (most) jobs when merging to main is a waste of resources,
and we don't do it by default.
- Fixes: #1061
|
|
- As of ea31e87029288bfe5897b1dd6a02cdc291946c9e, the all_commits
job works for branches that are not derived from main.
- Remove outdated rule.
|
|
|
|
- `openpgp` uses features that are only present in version 1.3.0 of
buffered reader. Adjust the dependency.
|
|
|
|
|
|
- Fixes #1060.
|
|
|