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

Secure SM_DATA initialization #4

Open
jovanbulck opened this issue Jun 28, 2017 · 0 comments
Open

Secure SM_DATA initialization #4

jovanbulck opened this issue Jun 28, 2017 · 0 comments
Labels

Comments

@jovanbulck
Copy link
Member

We cannot rely upon the untrusted main init procedure to initialize module-private memory. Moreover, upon enabling a protected module, a Sancus-enabled processor zeroes out the entire private data section.

To avoid having to always write your own initialization procedure, the compiler should generate an sm_init procedure, included in the SM's text section and automatically called upon the first invocation after enabling SM protection.

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