Closed rscarson closed 2 months ago
A new review of available-by-default ops has revealed Deno.core.ops.op_panic, which when called forces a panic in the thread containing the runtime.
Deno.core.ops.op_panic
This can be fixed by stubbing out the panic op:
Deno.core.ops.op_panic = (msg) => { throw new Error(msg) };
Other ops, such as op_read can only be used on resource-ids loaded into a table on the rust side, and therefore do not violate sandboxing
op_read
Affects 0.4.x up-to and including 0.6.0
0.4.x
0.6.0
Fixed in v0.6.1
A new review of available-by-default ops has revealed
Deno.core.ops.op_panic
, which when called forces a panic in the thread containing the runtime.This can be fixed by stubbing out the panic op:
Other ops, such as
op_read
can only be used on resource-ids loaded into a table on the rust side, and therefore do not violate sandboxingAffects
0.4.x
up-to and including0.6.0