Skip to content

add tidbits relevant to lavamoat #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
naugtur wants to merge 1 commit into
base: main
Choose a base branch
from
Open

add tidbits relevant to lavamoat #9

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions slides/slides.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -202,6 +202,8 @@ newGlobal.Object === globalThis.Object;
newGlobal.x === globalThis.x;
```

> non-configurable properties would need to become configurable on the copy for some use cases

---

#### Details - Properties can be selectively grafted
Expand Down Expand Up @@ -338,6 +340,10 @@ const source = new ModuleSource(
);
await newGlobal.eval("s => import(s)")(source);
```
---

To apply isolation in bundles resulting from running a build process, while under CSP with no `unsafe-eval` we may need to rely on [Module Declarations](https://github.com/tc39/proposal-module-declarations) producing an instance or a `ModuleSource` whose import via an importHook by the new global would not be considered an evaluation but a same-origin import.
---
Comment on lines +345 to +346
Copy link
Member

@kriskowal kriskowal Jul 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We do not need to wait for module declarations for CSP blessed module sources to come to bear. We already have that with import source and import.source, which if implemented by the host, may bless the module instance with origin information that would permit them to be executed under no-unsafe-eval. We also have to option of extending the ModuleSource constructor to accept a Trusted Type for the same effect.

Copy link
Member Author

@naugtur naugtur Jul 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Delayed to after plenary, I don't know what I want this to say.


<!-- visual customizations -->

Expand Down
Binary file modified slides/slides.pdf
View file
Open in desktop
Binary file not shown.