-
Notifications
You must be signed in to change notification settings - Fork 543
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
aesmd - EINIT returns 2 on startup #44
Comments
According to the Programming Reference, return code of 2 is Invalid Attribute. This could happen if your PSW is out of date with the prebuilt binaries. |
As far as I can tell, I am using the latest PSW built from master. I uninstalled, pulled the latest master, and did a clean rebuild/reinstall and the issue still happens. Is it possible the prebuilts are behind master? |
The interface between Linux-sgx and Linux-sgx-driver has been updated after 1.6 tag. |
@donporter - If AESMD starts correctly, i.e. you can obtain launch tokens for you enclaves, then the "EINIT returned 2" message is benign. The AESM first tries to load the Launch Enclave using a non-production signature/key, and then retries using a production signature/key if EINIT fails due to an invalid attribute, i.e. incorrect LE pubkey hash. The driver logs the EINIT failure as it is unaware that failure is expected (on some platforms). This issue can be closed unless there is an actual failure, the message itself is a "feature". |
I am on Ubuntu 16.04, using the latest master for linux-sgx and linux-sgx-driver. When I start aesmd, I get this message in dmesg:
[448620.384306] isgx: [8831:0x00007fd8aeb00000] EINIT returned 2
I assume this is not good. Any advice?
Thanks!
The text was updated successfully, but these errors were encountered: