| Age | Commit message (Collapse) | Author |
|---|
|
This reverts commit 2e1eec5fe4157a391a13554ff7df3075cfe043cc.
|
|
- Fixes #484.
|
|
- See #484.
|
|
- Make `cert::amalgamation::key` a public module.
- Move `cert::amalgamation::keyiter` to
`cert::amalgamation::key::iter`. Have `cert::amalgamation::key`
export its public symbols.
|
|
- This avoids the partial implementation imitating
std::option::Option, replacing it with std::result::Result.
- As a benefit, std::result::Result is in the prelude, simplifying a
lot of parsing loops.
|
|
|
|
|
|
- Change `mark_role_primary` to `role_into_primary`.
- Change `mark_role_primary_ref` to `role_as_primary`.
- Change `mark_role_subordinate` to `role_into_subordinate`.
- Change `mark_role_subordinate_ref` to `role_as_subordinate`.
- Change `mark_role_unspecified` to `role_into_unspecified`.
- Change `mark_role_unspecified_ref` to `role_as_unspecified`.
- Fixes #452.
|
|
- Previously, Message was polymorphic over the cookie. However, the
writer stack framework only has one user, and it likely ever will,
so I don't really see the point in complicating our interface.
|
|
- This aligns it with AED::symmetric_algo and SKESK::symmetric_algo.
|
|
- KeyID::as_slice and KeyID::from_bytes mirror each other. This
should be reflected in the functions' names. Also, as_bytes is
more descriptive.
- Same for Fingerprint::as_slice and Fingerprint::as_bytes.
- KeyHandle::as_slice renamed for consistency.
|
|
|
|
- Rename `ComponentBundleIter` to `ComponentAmalgamationIter` and
`ValidComponentBundleIter` to `ValidComponentAmalgamationIter`.
- Move module from cert::bundle to cert::amalgamation.
- Fixes 8ebaf6e4ada1cea0b9e6f6dfee61c22cfdc9748c.
|
|
|
|
|
|
- Change `mark_parts_public` to `parts_into_public`,
- Change `mark_parts_public_ref` to `parts_as_public`,
- Change `mark_parts_secret` to `parts_into_secret`,
- Change `mark_parts_secret_ref` to `parts_as_secret`,
- Change `mark_parts_unspecified` to `parts_into_unspecified`,
- Change `mark_parts_unspecified_ref` to `parts_as_unspecified`,
- Fixes #452.
|
|
|
|
|
|
- Previously, Message::new returned a writer::Stack, and Message was
just an empty struct. Unify the types. This makes sense, because
if you have a message, and encrypt it, you get a message.
- Make the writer module private. This is an implementation detail.
|
|
|
|
- Rename `KeyIter` to `KeyAmalgamationIter`, `ValidKeyIter` to
`ValidKeyAmalgamationIter`.
- Rename `cert/keyiter.rs` to `cert/amalgamation/iter.rs`.
|
|
- Rename `ComponentIter` to `ComponentBundleIter`, which is more
accurate.
- Rename the module from `cert/component_iter.rs` to
`cert/bundle/iter.rs`.
|
|
- Add the `UserID`, `UserIDAmalgamation` and
`ValidUserIDAmalgamation` types, and some associated methods.
- Replace the use of `UserIDBundle` with `UserIDAmalgamation` and
`ValidUserIDAmalgamation`.
|
|
|
|
- Cf. c4f087f886bd66f4177093569db615dc1c1e9e1d
|
|
|
|
- See #462.
|
|
- See #462.
|
|
|
|
- If looking up a binding signature fails, don't merely return None,
but an Err(_) that explains the lookup failure. For example, a
binding signature may be present, but it may not meet the policy.
- Fixes #460.
|
|
|
|
- Change ValidAmalgamation::cert to return a `&ValidCert` instead of
a `Cert`.
- Fixes #454.
|
|
- Previously, we transformed data and detached signatures into
signed messages on the fly, then used the streaming Verifier to
verify the message. However, this introduces a nontrivial
overhead, even if unnecessary copies are carefully avoided.
- Instead, specialize the streaming Decryptor to handle detached
signatures. use crypto::hash_buffered_reader to compute the
hashes over the data, then attach the computed signatures to the
signature packets, and use Decryptor's verification machinery.
- While this is arguably less elegant, it is much simpler, and a lot
faster. Notably, if we operate on files and can mmap them into
memory, we can compute the hash in one call to the compression
function. Verification of detached signatures is an important use
case, so this speedup outweighs the loss of elegance.
- Fixes #457.
|
|
- Expose ValidKeyAmalgamation::with_policy in the C FFI.
|
|
- Expose `ValidKeyAmalgamation::set_expiration_time` to the C FFI.
|
|
- Introduce `KeyAmalgamation` and `ValidKeyAmalgamation` to the C
FFI.
- Change pgp_cert_key_iter_next and pgp_cert_valid_key_iter_next to
return them instead of keys.
|
|
- Replace all usages of `to_hex` with formatting string with :X
specifier.
- Fixes #456.
|
|
|
|
- By explicitly printing to stderr, we can avoid the test's output
from being captured by Rust's test framework.
|
|
- Fixes linking tests and examples with ld --as-needed.
|
|
- Add a new Null Policy, which accepts everything.
|
|
- pgp_writer_stack_message should take a reference to the writer and
not take ownership of the writer.
- This is essential for the armor writer, which needs to be
explicitly finalized.
|
|
- Make the reference time an argument to pgp_cert_primary_user_id.
|
|
- Dropping a zeroed instant of that type is not safe as it contains
references.
|
|
- Use the anyhow crate instead of failure to implement the dynamic
side of our error handling. anyhow::Error derefs to dyn
std::error::Error, allowing better interoperability with other
stdlib-based error handling libraries.
- Fixes #444.
|
|
|
|
|
|
- Add two new traits: `Marshal` and `MarshalInto`.
- Implement them instead of `Serialize` and `SerializeInto`.
- Only implement `Serialize` and `SerializeInto` for data structures
that are normally exported.
- This should prevent users from accidentally serializing a bare
signature (`Signature`) when they meant to serialize a signature
packet (`Packet`), for instance.
- Fixes #368.
|
|
|
|
- Started in d183e12a3231e4c505f5f2cf48b6c1f881ad258a.
|
