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

Wrong security monitor size on secure bootstrapping #30

Closed
dayeol opened this issue Jan 22, 2019 · 0 comments
Closed

Wrong security monitor size on secure bootstrapping #30

dayeol opened this issue Jan 22, 2019 · 0 comments
Assignees
Labels
Bug Something isn't working

Comments

@dayeol
Copy link
Contributor

dayeol commented Jan 22, 2019

The security monitor spans (0x80000000-0x80200000)
and the last page (0x801ff000) is for secure bootstrapping parameters (e.g., attestation key, device pubkey, etc).
Currently, the last page is hard-coded as 0x802ff000 which is not protected by the PMP.

This is a mistake, and should be fixed as soon.

@dayeol dayeol added the Bug Something isn't working label Jan 22, 2019
@dayeol dayeol self-assigned this Jan 22, 2019
dayeol added a commit that referenced this issue Jan 23, 2019
This resolves #30
The security monitor size has been hard-coded as 0x2ff000, but actually
it's 0x1ff000
Bumped QEMU because the older QEMU has bug
@dayeol dayeol closed this as completed Jan 24, 2019
@dayeol dayeol mentioned this issue Feb 1, 2019
dayeol added a commit that referenced this issue Feb 1, 2019
dayeol added a commit that referenced this issue Sep 24, 2022
grg-haas pushed a commit that referenced this issue Feb 27, 2023
Fix build.sh to build with no arguments, fix Travis
grg-haas pushed a commit that referenced this issue Feb 27, 2023
Fix build.sh to build with no arguments, fix Travis
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant