Difference between revisions of "Low Integrity Code Generation"
From MgmtWiki
(→VS Code) |
(→References) |
||
| Line 10: | Line 10: | ||
[https://code.visualstudio.com/blogs/2022/11/28/vscode-sandbox Migrating VS Code to Process Sandboxing] describes the process of moving a (initially) 12 MB code generation platform to the use of ONLY low-integrity source code. | [https://code.visualstudio.com/blogs/2022/11/28/vscode-sandbox Migrating VS Code to Process Sandboxing] describes the process of moving a (initially) 12 MB code generation platform to the use of ONLY low-integrity source code. | ||
| + | |||
| + | ==Solution== | ||
| + | Stop trying to make [[Web App]]s into high-integrity solutions providers. | ||
==References== | ==References== | ||
[[Category: Browser]] | [[Category: Browser]] | ||
Revision as of 09:56, 9 March 2023
Full Title or Meme
The effort to create fully functional Web Apps has led to changes in the functionality of the browser sandbox to allow functionality, like FILE API, that can easily be exploited to create high integrity applications with low integrity code files.
Context
The W3C WICG (web incubation community Group)
Problems
VS Code
Migrating VS Code to Process Sandboxing describes the process of moving a (initially) 12 MB code generation platform to the use of ONLY low-integrity source code.
Solution
Stop trying to make Web Apps into high-integrity solutions providers.
