-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optional serde support #73
Comments
Here's the previous issue on serde support: RustCrypto/utils#979 We can add it, but unfortunately the serde data model lacks proper support for fixed-sized arrays, which is an issue I brought up on the other PR. This makes serializations of It might make sense to consider changing the |
Thanks for the context and the pointer to the serdect crate, I wasn't aware of it yet. The motivating paper on side-channel attacks on ser/de of keys also looks interesting.
This sounds rather annoying :/
The latest pre-release version (0.11.0-pre.3) has no serde feature. Or did you mean the latest stable? But as I understand it, From my point of view, an optional |
Generic serde support in |
Support for serializing `Array<T, U>` as a serde tuple. Unfortunately `serde` lacks first-class support for arrays, so this is the best we can do other than a length-prefixed slice-like serialization, which might also be worth considering. This seems like the most sensible place to start, though. Closes #73
Support for serializing `Array<T, U>` as a serde tuple. Unfortunately `serde` lacks first-class support for arrays, so this is the best we can do other than a length-prefixed slice-like serialization, which might also be worth considering. This seems like the most sensible place to start, though. Closes #73
generic_array::GenericArray
optionally implements serde's Serialize and Deserialize trait if the corresponding feature is enabled.I tried to update my dependency on blake2 to the current pre-release, but am blocked on the missing serde implementations on Array.
Are these planned for the future?
The text was updated successfully, but these errors were encountered: