| Age | Commit message (Collapse) | Author |
|---|
|
- Using `crypto::Signer`s has several benefits. First, it shifts
the decision which key to use to the caller, moving policy out of
the caller. Second, it forces the caller to deal with encrypted
keys. Finally, it allows us to use remote keys like smart cards
in the future.
- Fixes #142.
|
|
- Trait Parse introduces a uniform interface to parse packets,
messages, keys, and related data structures.
|
|
- The packet parser transparently strips armor now.
|
|
|
|
|
|
- Also, improve documentation and doctests.
|
|
- Fixes #112.
|
|
|
|
|
|
|
|
- Do not expose the `writer::Stackable` trait in the API. Instead,
use a tuple struct to wrap boxed objects of this kind.
- Add and use `writer::Stack::finalize()` and
`writer::Stack::finalize_all()` to pop one or all writers from the
stack.
|
|
- Also, simplify the example accordingly.
- Add an example for a normal signature.
|
|
- This implements the low-level functionality necessary to create
signatures using RSA, DSA, ECDSA, and EdDSA.
|
