Difference between revisions of "Low Integrity Code Generation"

Revision as of 13:34, 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.

Author: Tom Jones (This is a personal opinion that should not be attributed to any of my employers.)

Last Update: 2023-03-03

Context

The W3C WICG (web incubation community Group) - from the charter^[1]

• The Web Incubator Community Group (WICG) provides a lightweight venue for proposing and discussing new web platform features.
• W3C Community Contributor License Agreement (CLA) mostly deals with IP.
• The Community Group will accept and discuss any proposal for a web platform feature that would be implemented in a browser or similar user agent. Any suggestions, pull requests, issues, or comments made about a proposal fall under the CLA.
• The group will conduct all of its technical work on its GitHub repositories (and not in mailing list discussions). This is to ensure contributions can be tracked and to ensure that engagement will scale to a large number of proposals.
• WICG - File System Access AP

Mandatory Integrity Checking (MIC)

Problems

Any Web App that deals with low-integrity data should be allowed to impact high-integrity functionality. The example used here is VSCode, a Microsoft code generation application, but any Web App that transitions low-integrity input to high-integrity output would have the same issues.

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.

References

1. ↑ W3C Web Incubator Community Group Charter (2023-02-22) https://wicg.github.io/admin/charter.html