17 lines
1.4 KiB
Markdown
17 lines
1.4 KiB
Markdown
# Security
|
|
|
|
pplus-core reads programs and runs them inside its own interpreters: pseudo, Mojo and x86-64 are interpreted by JavaScript written here, with a step limit, and nothing a program says is ever handed to JavaScript's `eval` or to a shell.
|
|
The prover and the fuzzer work on the same trees.
|
|
A program that makes an engine crash (an exception escapes), hang past its step or time limits, use memory without bound, or reach anything outside the program's own state is a security issue, because pplus-web runs these engines on whatever a link carries.
|
|
So is a "proved" verdict for something a run breaks, which is a soundness bug: it would let a student trust a wrong program.
|
|
|
|
Some tasks run real tools on your machine, and those run what you give them: `pixi run mojo-local`, `mojo-fuzz` and `library-check` build and run Mojo, C and Python programs from this repository and from the library, and `mojo-verify`, `mojo-verify-item`, `play` and `library-verify-mojo` send the corpus's programs and the library's Mojo references to godbolt.org.
|
|
Run them on a checkout you trust.
|
|
|
|
Report a problem to Alex M. Maldonado at alex@scient.ing, with the program that shows it 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 the latest commit on `main` gets fixes.
|