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

ERROR. : SGX_ERROR_UNRECOGNIZED_PLATFORM #912

Open
mapleshi opened this issue Aug 6, 2022 · 2 comments
Open

ERROR. : SGX_ERROR_UNRECOGNIZED_PLATFORM #912

mapleshi opened this issue Aug 6, 2022 · 2 comments

Comments

@mapleshi
Copy link

mapleshi commented Aug 6, 2022

✔ SGX instruction set
✔ CPU support
✔ CPU configuration
✔ Enclave attributes
✔ Enclave Page Cache
SGX features
✔ SGX2 ✔ EXINFO ✘ ENCLV ✘ OVERSUB ✔ KSS
Total EPC size: 4.0GiB (no integrity protection)
✘ Flexible launch control
✔ CPU support
? CPU configuration
✘ Able to launch production mode enclave
✔ SGX system software
✔ SGX kernel device (/dev/isgx)
✔ libsgx_enclave_common
✔ AESM service
✔ Able to launch enclaves
✔ Debug mode
✘ Production mode
✔ Production mode (Intel whitelisted)

🕮 Flexible launch control > CPU configuration
Your hardware supports Flexible Launch Control, but whether it's enabled could not be determined. More information might be available by re-running this program with sudo. Would you like to do that?
(not supported yet)

debug: Error reading MSR 3Ah: Failed to load MSR kernel module
debug: cause: Failed to load MSR kernel module
debug: cause: Failed executing modprobe
debug: cause: No such file or directory (os error 2)

More information: https://edp.fortanix.com/docs/installation/help/#flc-cpu-configuration

🕮 SGX system software > Able to launch enclaves > Production mode
The enclave could not be launched. This might indicate a problem with FLC.

debug: failed to load report enclave
debug: cause: failed to load report enclave
debug: cause: The EINITTOKEN provider didn't provide a token
debug: cause: aesm error code GetLicensetokenError_6

More information: https://edp.fortanix.com/docs/installation/help/#run-enclave-prod

You're all set to start running SGX programs!
Generated machine id:
[171, 55, 166, 151, 183, 51, 195, 76, 43, 102, 176, 129, 105, 122, 214, 170]

CPU Cores:
64

Encoded runtime info:
[1, 0, 0, 0, 171, 55, 166, 151, 183, 51, 195, 76, 43, 102, 176, 129, 105, 122, 214, 170, 3, 246, 143, 56, 28, 234, 1, 85, 49, 253, 88, 64, 45, 156, 203, 165, 240, 38, 23, 125, 218, 226, 71, 55, 9, 143, 153, 109, 167, 226, 76, 174, 6, 8, 64, 0, 0, 0, 1, 0, 0, 0]
Testing RA...
aesm_service[15]: [ADMIN]EPID Provisioning initiated
aesm_service[15]: The Request ID is a4046d830a1f4122be1b266cc28564f8
aesm_service[15]: The Request ID is 334eb818488d4e35a3006f33d456fd23
aesm_service[15]: [ADMIN]EPID Provisioning protocol error reported by Backend (6)
aesm_service[15]: [ADMIN]EPID Provisioning failed
thread '' panicked at 'error while doing remote attestation: SGX_ERROR_UNRECOGNIZED_PLATFORM', src/lib.rs:448:132
fatal runtime error: failed to initiate panic, error 5
./start_sgx_detect.sh: line 20: 41 Illegal instruction (core dumped) ./app

[ phala_scripts_check_sgxtest ] unknown error!

%%%%%%%%%%%
my cpu is Intel(R) Xeon(R) Silver 4314 CPU @ 2.40GHz
Dose it suport SGX1.0?
thanks very much.

@mapleshi
Copy link
Author

Does it any plan to suport sgx2.0 ?

@jasl
Copy link
Collaborator

jasl commented Aug 10, 2022

DCAP support is working in progress, I guess we're the first public product embraces DCAP attestation, so there's no reference that made things difficulty.

BTW, PRuntime can be ran on SGX 2.0 hardwares (Ice Lake-SP and Sapphire Rapid), but they're lacking EPID remote attestation support, only DCAP.

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

No branches or pull requests

2 participants