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.

Sign up for GitHub

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

Jump to bottom

What about SES and WASM? #8

Open
erights opened this issue Mar 27, 2016 · 3 comments
Open

What about SES and WASM? #8

erights opened this issue Mar 27, 2016 · 3 comments

Comments

@erights
Copy link
Collaborator

erights commented Mar 27, 2016

On a recent post on cap-talk I claim that WASM, by virtue of operating within the JavaScript heap and some other assumptions, would inherit the integrity/security properties of SES without need for any additional mechanism. (See that message for the full rationale.)

Need to verify this with WASM experts.
@benjamingr
Copy link

I think that with asm.js it is pretty clearly the case but as WASM adds capabilities it might diverge and this might no longer hold. Namely, things like threading that are on the roadmap pose a risk.

@erights
Copy link
Collaborator Author

erights commented Apr 15, 2016

"threading"? "roadmap"? links?

@benjamingr
Copy link

See discussion here: WebAssembly/design#104

Also see https://github.com/WebAssembly/design/blob/58d5ad28712fc634a0f3dbe443177410879ae6da/PostMVP.md#threads

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@erights @benjamingr