@Jamesernator technically, if you can set custom any built-in objects, you can customize the environment in which the code is executed – practically, you can replace any APIs with your own stubs and this is pretty sandbox-ish

Yes, but ShadowRealm isn't creating the sandbox, you are. You might as well define:

class Sandbox {
    #shadowRealm = new ShadowRealm();
    
    constructor() {
        // clean the shadow realm of unsafe globals
    }
}

to declare a "Sandbox".

practically, you can replace any APIs with your own stubs and this is pretty sandbox-ish

Actually no, if Node does implement what I mentioned, then import("node:fs") would allow code in a ShadowRealm to gain access to fs regardless of what globals you delete or replace.

If you want actual sandboxing, you need both this proposal and at least minimum the compartments proposal. Even then you probably want the ses proposal if you're actually going to be running untrusted code.

Why not call it a Sandbox? #368

Description

devlatoopenedon Jun 5, 2022

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

devlato
openedon Jun 5, 2022