Skip to content

Some common problems whilst building Veracruz, and their solution.

Christopher Haster edited this page Feb 23, 2021 · 6 revisions

An unordered list of common issues and their solutions (More to be added).

Error SGX_ERROR_NO_DEVICE

Make sure you have the SGX driver installed. Note that this may break of your kernel is updated. See the What to do when your kernel version changes section in the BUILD_INSTRUCTIONS.md

value-bag match is not allowed in a const

If you get this error message during compilation:

error[E0658]: `match` is not allowed in a `const`

This is currently happening due to a mismatch of nightly vs stable rust and crate dependencies. I can currently work around this by using Cargo.lock files from a previous version of Veracruz, but that's not really a solution for anyone else. See https://github.com/veracruz-project/veracruz/issues/60 for fixing this.

Outdated git dependency

the package `mexico_city_enclave` depends on `ring`, with features: `nitro` but `ring` does not have
 these features.

If you see an error message reference a missing feature in a dependency, this most likely means that the Cargo.lock file is out of date. Go into the crate directory (mexico_city_enclave in this case), delete Cargo.toml, and refetch again cargo fetch. This should find a commit with the correct feature set.

Or delete all Cargo.lock files, since this is likely not the only one out of date:

rm $(find -name 'Cargo.lock')

I think https://github.com/veracruz-project/veracruz/issues/60 fixes this.

Submodules

make[1]: Leaving directory '/work/veracruz/mexico-city'
--- stderr
error: File not found within search paths: sgx_tstd.edl

This most likely means you did a normal clone and don't have the most recent submodules.

This command will update submodules:

git submodule update --init --recursive

Invalid IAS_TOKEN

thread 'actix-rt:worker:2' panicked at 'no entry found for key', /work/veracruz/tabasco/src/attestation/sgx.rs:654:21

If your IAS_TOKEN is invalid, the response from Intel's attestation service does not contain the X-IASReport-Signature header, causing this error.