-
Notifications
You must be signed in to change notification settings - Fork 95
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
aa: Rename Occlum attester to SGX attester and add Gramine support to it #167
aa: Rename Occlum attester to SGX attester and add Gramine support to it #167
Conversation
a05268d
to
6bdc7fb
Compare
} | ||
} | ||
SgxLibOsType::Gramine => { | ||
std::fs::write("/dev/attestation/user_report_data", report_data_bin)?; |
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.
Do we also need occlum_dcap
dependency if gramine is the libos? I mean if not, we can avoid bringing occlum_dcap
to decrease the footprint.
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.
we don't need it but I did not want to introduce new features but keep only one "SGX DCAP" feature.
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.
Ok. Let's handle this in future when footprint is actually an obstacle for enclave-cc.
I just rebased to fix merge conflicts. Let's see the results now. Update: Seems to be OK: https://github.com/confidential-containers/guest-components/actions/runs/5573122545/jobs/10179974921?pr=167 |
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, thanks!
Hi @mythi Can you rebase this PR? |
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
SGX DCAP Attester checks that the evidence passed in is base64 encoded SHA384 and fails if the base64 decoded input does not match the expected length. Therefore, "test".into() won't work and errors. Fix by using the same hasher as the KBS protocol. Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
done |
No description provided.