Skip to content
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

ML-DSA Private key sizes 32bytes or expanded? #94

Open
johngray-dev opened this issue Dec 12, 2024 · 0 comments
Open

ML-DSA Private key sizes 32bytes or expanded? #94

johngray-dev opened this issue Dec 12, 2024 · 0 comments

Comments

@johngray-dev
Copy link
Collaborator

I think more discussion is needed about whether the private key format should allow the expanded format as well as the seed. If an implementation only had access to the expanded format, and needed to export the key, then it may not have access to the seed. If there is no way to support this in a reasonable way, then there WILL be operational issues down the road.

  • Max suggests we could have a separate section for the private key. For the traditional component, if we know the keysize, we can look for 32+trad or expanded mldsa+ trad and know which one to use. That would be more efficient than using the first 32 bytes, expanding them (which will work even if the key is already expanded).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant