-
Notifications
You must be signed in to change notification settings - Fork 112
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
Add invariants on Wasm Execution #3671
Comments
A few detail points:
|
Nice! Maybe also related are our reasons for choosing wasmi as interpreter. |
We should also add the limitation that Oak Functions is currently not able to terminate the execution of a request. Furthermore, as a precaution, the Oak Functions ABI does not expose any kind of timing functionality to the request's logic. |
Related #3079 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Oak Function leverages and relies on Wasm and wasmi to isolate one user request from each other.
We have the following invariants:
We need to clarify whether executing two user requests in parallel can lead to contention-based side channel attacks, but for now, Oak Functions only executes a single user request at the time.
I want to state the invariants in a README in oak_functions/wasm and connect to our code, simlar to the invariants for lookup data.
Related: #3449 .
Anything missing @conradgrobler @tiziano88 ?
The text was updated successfully, but these errors were encountered: