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

Refactor: Offer single-step library abstraction #2

Open
jovanbulck opened this issue May 16, 2018 · 1 comment
Open

Refactor: Offer single-step library abstraction #2

jovanbulck opened this issue May 16, 2018 · 1 comment
Labels

Comments

@jovanbulck
Copy link
Owner

SGX_STEP_PLATFORM and SGX_STEP_TIMER_INTERVAL and actual timer configuration AEP code should better be encapsulated in libsgxstep plus a common Makefile.config, such that the actual application AEP callback code can focus exclusively on gathering side-channel information.

@jovanbulck jovanbulck changed the title Cleanup platform-specific timer configuration code Refactor: Offer single-step library abstraction Feb 4, 2020
@jovanbulck
Copy link
Owner Author

jovanbulck commented Feb 4, 2020

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 time in the attack application.

Instead, libsgxstep should offer a convenient start/stop_single_step() abstraction that encapsulates all of the low-level details and platform-specific code. At this point we could also take care to enable/disable the APIC timer and pin to a specific CPU core etc.

dn0sar added a commit to dn0sar/sgx-step that referenced this issue Jun 29, 2020
Added demo bench app to showcase the changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant