-
Notifications
You must be signed in to change notification settings - Fork 259
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
Upgrade to Intel SGX Linux 2.4 Release #48
Comments
Hi @tomtau , I'm busy working with this but encountered a lot of problems. For example, v2.4 has some bugs and I just filed PR and waiting for response. And I have a pending PR at Rust to fix xargo build failure in most recent Rust nightly (issue here). Here are a minimal solution for v2.4:
Plan: Best, |
Update: PR to Rust has been merged. Still waiting for Intel's response. |
Update: found another linking problem when linking with libsgx_tstdc.a, about multiple definition of |
Update: all existing PRs to Rust has been merged and nightly-2019-01-09 works well on my unreleased version. Intel confirms that the problem of report checking is a bug, but the fix is being tested and has not been merged. So now I have two choices: (1) wait until 2.4.1 and skip 2.4 Which one do you guys prefer? |
Probably wait for 2.4.1? |
Yeah I'll say wait for 2.4.1, |
@tomtau @elichai |
BTW, do you know if there's some mailing list or subscription that I can get notified for these vulnerabilities? |
@elichai you should receive them if you're enrolled in the SGX Program (which you'll need to be in order to sign production enclaves) |
@tarcieri I am enrolled, but all I get from them is some spam on compute vision lol |
@dingelish Is there a way to know when 2.4.1 will be released? if not It might be better to use a patch because a couple of changes with unstable features getting stable (specifically const_fn) makes using some libraries a bit more difficult |
@elichai Yesterday I asked Intel the same question and they answered that the current 2.4 is exactly 2.4.100. There is no 2.4.1. It seems that the current 2.4 has already patched IPP bug (but not the sig verification bug which is fixed later). I can provide a branch to support recent Rust nightly today. And I'll need another few days for documentation and rust-stable branch. Is this ok for you? I think the next v1.0.5 could be ready next week. |
Sounds great. |
https://01.org/node/29957
The text was updated successfully, but these errors were encountered: