2.6 KiB
Security
Programming+ is a static site: the server sends files and keeps nothing.
There are no accounts. What a visitor writes stays in their browser: localStorage keeps their work, their saved versions, their recent compiles and their preferences, and a share link carries a program in the part of the URL after #, which browsers do not send to the server.
The site sends a program somewhere in one case: Compile & run posts the program's text, its input and the build options to Compiler Explorer (godbolt.org), whose privacy policy says what it keeps.
The page, its scripts, its styles and its fonts all come from the site itself; no other server is asked for anything (tests/site-data.test.mjs holds this, and the Content-Security-Policy in docs/Caddyfile enforces it in the browser).
In scope
The site at pplus.scient.ing and this repository, in particular:
- State from a link. A share link, an embed URL and a
.pplus.jsonfile are decoded into the app's state (src/core/state.ts). A crafted one that runs script, reaches another origin, makes the page unusable, or changes what another visitor's saved work holds is a vulnerability. - Text that reaches the page. Programs, their output, compiler messages, routine notes and every other string that ends up in the DOM, the views rendered by the Quarto extension included.
- Embeds. The app inside an iframe on another site (
#/embed/...), the messages it exchanges with the page around it, and which sites may frame it (theframe-ancestorsrule indocs/Caddyfile). - What goes to godbolt.org. Anything other than the program, its input and the build options, or a request sent without the visitor pressing Compile & run.
- The engines, through the site: a program that makes pseudo, Mojo or x86-64 hang the page past its step limits or crash it (pplus-core's
SECURITY.mdhas the engines' side).
Out of scope
godbolt.org itself (report to Compiler Explorer), the hosting provider, the volume of requests a visitor can make, and a visitor running code on their own machine with the repository's tasks.
Reporting
Report a problem to Alex M. Maldonado at alex@scient.ing, with the link or file that shows it, the browser, and what happened. You will get an acknowledgment within a week. We promise no response time beyond that; one person maintains Programming+. Please do not open a public issue for a problem that could hurt someone else until a fix is out.
Only what is deployed from the latest commit on main gets fixes.