Comment by pjmlp
3 hours ago
Easy, see other bytecodes with bounds checking opcodes, and where use of unsafe bytecodes taint the executable on the verifier, which then requires explicit execution permission.
3 hours ago
Easy, see other bytecodes with bounds checking opcodes, and where use of unsafe bytecodes taint the executable on the verifier, which then requires explicit execution permission.
Taint it how? What kind of permissions? Your fix is a pop up warning on unsafe code?