Error while loading shared libraries: libsecret_prov_verify_epid.so

[范佳峰]

Hi,

when I run graphene `End-To-End Confidential PyTorch Workflow`example,I get some error that i have no idea to figure it out,so i Ask you for help。

I use EPID remote attestion,when i run `./secret_prov_server_epid &` command,

it is said:

[1] 4896
./secret_prov_server_epid: error while loading shared libraries: libsecret_prov_verify_epid.so: cannot open shared object file: No such file or directory

it's strange because i can found the  libsecret_prov_verify_epid.so file in the same directory(graphene/Examples/pytorch-confidential).

I tried mkdir libs and put it to libs directory,it also get the same error.

 other Examples can run correct.I'm stuck with this remote attestion.

and 

if i ignore this error and contuine，

command `SGX=1 ./pal_loader ./pytorch pytorchexample.py`

get this error:

error: aesm_service returned error: 12 

error: load_enclave() failed with error -1

so I checkd aesmd secvice:

[load_qe ../qe_logic.cpp:641] Error, call sgx_create_enclave QE fail [load_qe], SGXError:4004.
Failed to load QE3: 0x4004

and 

[ADMIN]EPID Provisioning failed due to network error.

here is some infos:

os: ubuntu 18.04,

sgx driver :ott driver,

sgx remote attestion:EPID,

SGX supported by CPU: true
SGX1 (ECREATE, EENTER, ...): true
SGX2 (EAUG, EACCEPT, EMODPR, ...): false
Flexible Launch Control (IA32_SGXPUBKEYHASH{0..3} MSRs): true
SGX extensions for virtualizers (EINCVIRTCHILD, EDECVIRTCHILD, ESETCONTEXT): false
Extensions for concurrent memory management (ETRACKC, ELDBC, ELDUC, ERDINFO): false
CET enclave attributes support (See Table 37-5 in the SDM): false
Key separation and sharing (KSS) support (CONFIGID, CONFIGSVN, ISVEXTPRODID, ISVFAMILYID report fields): false
Max enclave size (32-bit): 0x80000000
Max enclave size (64-bit): 0x1000000000
EPC size: 0x5e00000
SGX driver loaded: true
SGX PSW/libsgx installed: true
AESMD running: true

I'm lost and don't know what to do,I wish you can give me some advice.

Thanks a lot~

from Alimail Windows

[盘古张]

Looks like I hit the same issue, What's the latest status for this question?