-
Notifications
You must be signed in to change notification settings - Fork 32
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
mgm: Generalize TDES logic to enable other algorithms #588
base: main
Are you sure you want to change the base?
Conversation
8995d74
to
7e437c9
Compare
4df88c6
to
622d989
Compare
@str4d if you can rebase and remove draft we can get this reviewed |
622d989
to
aaae123
Compare
Rebased on |
aaae123
to
4c00e0b
Compare
Force-pushed to fix a rebase bug. |
Co-authored-by: Greg Bowyer <[email protected]>
4c00e0b
to
ca197e1
Compare
Force-pushed to update a new test for the generalization. |
/// TODO: Can we distinguish DES from AES-192? Or do we take `C` as a parameter and | ||
/// require the caller to know the type of the bytes they are parsing? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure you can take a generic cipher instance since you're trying to map concrete ciphers to an enum. I think you either need some kind of separate algorithm identifier enum you can pass as a parameter, or to have separate constructor functions per algorithm.
|
||
/// Derives a management key (MGM) with the given algorithm from a stored salt. | ||
/// | ||
/// TODO: Is this supported for AES? Is the algorithm supposed to be dynamic? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No idea here
Part of #330.
Includes #584 because I don't have write permissions on the repo and thus can't create stacked PRs directly.