-
Notifications
You must be signed in to change notification settings - Fork 52
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
ek, ak abstractions: allow to specficy exact key type #414
ek, ak abstractions: allow to specficy exact key type #414
Conversation
ad49441
to
d909944
Compare
9ba573f
to
db71335
Compare
2630900
to
f0575ed
Compare
@ionut-arm the Original The major change introduced is that now create_ak, also requires a key algorithm specified. |
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.
Thanks for the new and improved patch!
f0575ed
to
309e699
Compare
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.
Thanks for all the changes! LGTM now, just left a nit comment, but otherwise happy to merge.
Also, I think we can merge despite the MSRV-related failure, we'll have to decide what to do with log
.
309e699
to
7bb9f79
Compare
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.
LGTM 👍
I am not against this. But is it not possible to achieve the same thing using the KeyCustomization trait? And if it is should we really have two ways of doing the same thing? |
@Superhepper for
I think that changing the key type is a common enough (for example swtpm uses for ECC Nist P384) to provide an simple way to specify it. |
This adds support other keys than RSA2048 and ECC Nist P256. Signed-off-by: Thore Sommer <[email protected]>
7bb9f79
to
04a42ea
Compare
@ionut-arm @Superhepper would it possible to backport this to 7.X? This is currently the main blocker for us to enable ECC fully in the rust Keylime agent, see: keylime/rust-keylime#513 |
Yeah, I am not sure if I have the time to do it any time soon but it is just a matter of writing a PR with changes for the 7.y.x branch instead. |
I tried to adapt your code to get it to work under the 7.x.y branch. #546 |
This takes the following PRs and from the main branch and adapts them so that they can be merged into the 7.x.y branch: \parallaxsecond#464 (By Ionut Mihalcea <[email protected]>) \parallaxsecond#414 (By Thore Sommer <[email protected]>) Co-authored-by: Jesper Brynolf <[email protected]> Co-authored-by: Thore Sommer <[email protected]> Co-authored-by: Ionut Mihalcea <[email protected]> Signed-off-by: Jesper Brynolf <[email protected]>
This takes the following PRs and from the main branch and adapts them so that they can be merged into the 7.x.y branch: \parallaxsecond#464 (By Ionut Mihalcea <[email protected]>) \parallaxsecond#414 (By Thore Sommer <[email protected]>) Co-authored-by: Jesper Brynolf <[email protected]> Co-authored-by: Thore Sommer <[email protected]> Co-authored-by: Ionut Mihalcea <[email protected]> Signed-off-by: Jesper Brynolf <[email protected]>
This adds support other keys than RSA2048 and ECC Nist P256.