evervault/node-secureworker

meteor paths hardcoded

Closed this issue · 2 comments

wh0 commented
  • where the enclave signing key is
  • where the enclave DLL is

the API for this package has no way of passing this information in

mitar commented

Removed. When creating a secure worker you now specify the path to .so file.

mitar commented

Not sure what happens if the same .so file is provided for two scripts. Is enclave established only once, or once for each file. It seems we call this every time we create a new instance of secure worker:

sgx_create_enclave(file_name, SGX_DEBUG_FLAG, &launch_token, &launch_token_updated, &enclave_id, NULL)