Closed henrylyons closed 1 year ago
It was a deliberate design decision to keep cryptographic operations out of this crate, and just to focus on the COSE data structures, and there are no plans to change that.
The existing entrypoints should hopefully make it straightforward to just plug in whatever crypto crate the user wants (e.g. in Android that's BoringSSL, elsewhere might use Tink-Rust, or ring, or …).
Happy to consider suggestions that might make that easier / more ergonomic though (cf. #18 in the past).
Currently, coset users have to provide closures to perform signing and verification operations. Do you have any plans to implement these operations in coset itself, or a separate crate? This functionality would be valuable for the Rust community and COSE users.