-
Notifications
You must be signed in to change notification settings - Fork 50
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
adding oesign signing engine test #1428
Conversation
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 work, @salsal97
tools/myst/host/package.c
Outdated
argv[0], | ||
"sign", | ||
rootfs_file, | ||
pem_file, // TODO: maybe I need to take this out |
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.
Can you make this null and see if it works? You should not need a pem file.
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.
Does oesign need a pem file with the signing engine?
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.
It does not need one, null seems to work. Will remove the comment. The thing here is we use positional arguments, so if we do not have a pem file it would potentially be a breaking change for everyone..
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.
Can we let people specify "NULL" as a command line param.
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.
Definitely, they can already do that. Tested it out
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.
Added that to this test so we can maintain is as the recommended way to use signing engines
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.
Looks great. Thanks for doing this Saloni!
As we are testing |
@@ -497,6 +498,7 @@ int _sign(int argc, const char* argv[]) | |||
pem_file, | |||
NULL, | |||
NULL, | |||
NULL, |
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.
Did the oesign()
signature change?
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.
Yeah it did
48a00b4
to
e0bf867
Compare
This test tests the mystikos support for signing engine via oesign. Adopted from https://github.com/openenclave/openenclave/pull/2455/files.