-
Notifications
You must be signed in to change notification settings - Fork 8
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 for SymmetricKey, AsymmetricSecretKey and AsymmetricPublicKey #26
Comments
Yes, I've been thinking about this as well. I'm writing up some thoughts on your PR comments right now. Will submit in a few. |
I'd like to pick this up, is there any more information that I'd need? If you're okay with it, I'd like to contribute support for the remaining PASERK key types, maybe sometime later. Picking this up should get me accustomed to the codebase. |
Hi @SanchithHegde, Great to hear you're interested in this!
I don't know how comfortable you are with Rust, but I'll try to collect what I think the initial thoughts were here. This issues scope includes at least the standard PASERK formats Additionally, it would probably also be worthwhile to add the optional Regarding adding support for other PASERK formats, this would also be nice to have added. Though we should probably have a look at them and prioritize those that make more sense to support first, compared to others. Further, that ought to go into a different issue if we start this up. If you have any other questions now or later, feel free to ping me. |
Thanks for specifying the requirements, I'll work on it.
That is indeed what I had in mind as well, let's take it up on a separate issue. |
I think allowing the keys to be serialized to and deserialized from PASERK strings would make sense.
This would be a follow up to #23.
The text was updated successfully, but these errors were encountered: