Age | Commit message (Collapse) | Author |
|
- See #498.
|
|
|
|
- See #498.
|
|
|
|
- See #471.
|
|
- Implement IntoIter and Deref to &'a [MessageLayer<'a>], drop the
custom iteration structs.
|
|
- Align Cert::set_expiration_time with
KeyAmalgamation::set_expiration_time, i.e. return the signatures
instead of merging them directly.
- Fixes #491.
|
|
|
|
- Don't export CertValidity, KeyringValidator, KeyringValidity, or
MessageValidity.
- Fixes #490.
|
|
- Arbitrary could generate identical user ids, but we rely on the
fact that they are different. Make sure that is the case.
|
|
- Keyring is spelt keyring, not key ring.
- Cf. https://tools.ietf.org/html/rfc4880#section-3.6
|
|
- See #466.
|
|
- This will hopefully make it harder to overlook.
|
|
- See #471.
|
|
|
|
|
|
- Return revocation keys listed on any User ID's self signature in
addition to those listed on direct key signatures.
|
|
- Change `ValidKeyAmalgamation::set_expiration_time` to return a
`Result<Vec<Signature>>` instead of a `Result<Vec<Packet>>`.
|
|
- Make MessageValidator `pub(crate)` instead of `pub`.
- Move doctests into unit tests as doctests cannot access `pub(crate)`
APIs.
- Fixes #490.
|
|
- Make CertValidator `pub(crate)` instead of `pub`.
- Remove unused methods.
- Mark `push_token` as `#[cfg(test)]` as it is used only in tests.
|
|
- Add KeyID::to_hex.
- Add KeyID::from_hex.
- Add Fingerprint::to_hex.
- Add Fingerprint::from_hex.
- Fixes #456.
|
|
- Change `Cert::merge_packets` to take an `IntoIterator` instead of
a vector.
- This change simplifies the most common case of passing in a single
packet, and doesn't make the second most common case of passing in
a vector of packets any more complicated.
|
|
- Implement `IntoIterator` for the `Packet` enum, and all of its
variants.
- Having this means we don't need to do something like
`std::iter::once(p)` when we need an iterator over a packet.
|
|
- Convert Cert::try_from(PacketPile::from(packets)) into
Cert::try_from(packets).
- Fixes #496.
|
|
- Drop `Cert::from_packet_pile`.
- Fixes #462.
|
|
- Fixes 3accc10973272de29f098c5db11951a122238d99.
- Fixes #495.
|
|
- Rename `Cert::revoke_in_place` to `Cert::revoke`.
- Return the revocation certificate; don't merge it.
- Fixes #485.
|
|
- Rename `Cert::revoked`, `ValidCert::revoked`,
`ValidAmalgamation::revoked`, and `ComponentBundle::revoked` to
revocation_status to more accurately match what it does.
- Don't rename `ValidComponentAmalgamationIter::revoked` or
`ValidKeyAmalgamationIter::revoked`. They don't return the
revocation status; they check whether the key is revoked.
|
|
- When extending the expiration on the primary key, don't create a
new binding signature for revoked User IDs. If the revocation is
a soft revocation, then this will cause the User ID to become
valid again.
|
|
- Fixes #495.
|
|
|
|
|
|
|
|
- Add a function to convert a vector of `Packet`s to a `Cert`.
|
|
- Don't assume that the current binding signature should be used;
include a reference time.
|
|
- See #466.
|
|
- Add Examples to all public functions.
- Add example armored message to the header.
- Fix wording.
- Fixes #468.
|
|
- Rename all calls to `Builder` with `SignatureBuilder`.
- Fixes #481.
|
|
- This adds a new frontend to Sequoia that implements the Stateless
OpenPGP Command Line Interface.
- Compared to sq, sop has a much smaller feature set and hence a
smaller set of dependencies. It is less opinionated, and tries to
faithfully implement the SOP protocol. We will use it to test
Sequoia using the OpenPGP Interoperability Test Suite.
|
|
- We finalize the writer stack at the end of the streaming
operation, but we build the filters using the builder pattern.
|
|
- This allows customization of the generated signatures.
|
|
|
|
|
|
- Previously, when creating an armored message using the
armor::Writer and the streaming serialization interface, one had
to finalize both the writer stack and the armor writer, which is
unergonomic, not obvious, and error prone.
- This filter properly finalizes the armor writer when the writer
stack is finalized.
- Fixes #453.
|
|
|
|
|
|
- Add a new constructor that takes headers. This allows us to make
the header argument polymorphic.
|
|
|
|
|
|
- Previously, armor::Writer::drop made an effort to finalize the
filter. This, however, is only a best-effort mechanism: It cannot
report errors.
- Because of this, we now believe that it actually exacerbates the
problem of downstream users not finalizing the filter: It will
work most of the time, but sometimes fail.
|