Skip to content
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

Closed
donporter opened this issue Nov 13, 2016 · 4 comments
Closed

aesmd - EINIT returns 2 on startup #44

donporter opened this issue Nov 13, 2016 · 4 comments
Labels

Comments

@donporter
Copy link

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!

@ENOTTY
Copy link

ENOTTY commented Nov 13, 2016

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.

@donporter
Copy link
Author

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?

@zhaohuidu
Copy link
Contributor

The interface between Linux-sgx and Linux-sgx-driver has been updated after 1.6 tag.
If you have updated one of them from 1.6 tag to latest code, you should update the other one too.
It is likely that unmatched version used

@sean-jc
Copy link

sean-jc commented Jan 25, 2017

@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".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants