Jo Van Bulck

single-stepping code is messy now -- applications have to copy the skeleton from `app/bench/main.c` and directly use libsgxstep's low-level apic and page table manipulations to build the single-stepping primitive each...

Thank you for opening this issue and the suggestion! Yes, I agree this is currently left unclear, so I hope to make some time next week to improve the documentation...

some relevant notes on moving fwd here; currently we rely on the following patches (which can probably be further reduced as outlined): - [ ] `sgx_get/set_aep`: this is the only...

idea to look into: maybe we can simply replace all `enclu` instructions in VDSO and shared libraries with `ud2` and trap these with a users-space signal handler to automatically redirect...

Hi George, No, this error should be unrelated to this issue. The linker error you get is because your SGX-SDK installation was not properly patched to export the needed `sgx_get_aep`...

If you get this undefined symbol error, it basically means you have to make sure you're loading the patched SDK urts library. Make sure to purge any SGX libraries installed...

Hm this indicates that there's a problem with creating the enclave, not sgx-step itself. The error is thrown by the Intel SGX-SDK code, see also this related issue: https://github.com/jovanbulck/sgx-step/issues/34 In...

Following up @wuyifancaixukyun , not sure if you already found a solution, but this error means that you didn't properly link to the patched SDK. Normally this should be fine...

Elementary CI is now integrated in GitHub Actions to: 1. Build and load `/dev/sgx-step` 2. Patch and build the `linux-sgx` Intel SDK and PSW 3. Build `libsgxstep` and sample applications...

Hi aegis, The plan is to refactor SGX-Step to make it easier to interface with different SDKs and LibOSs, todo as documented in #28 . However, I have not found...