-
-
Notifications
You must be signed in to change notification settings - Fork 654
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
Syscall review #4205
Labels
code
Code improvements
Comments
we also want to be able to accelerate general sha256 usage so if the sha256 syscalls are "secure" in that they don't interfere with one another, we want to keep this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Followup for #4188
We added (most of) syscalls to match the current usage in firmware, but this is not necessarily correct.
Some of them might be too low-level and deserve redesign, these are main candidates:
But we should reconsider more or less each syscall so that we don't expose stuff we don't really need to.
The text was updated successfully, but these errors were encountered: