Skip to content
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.

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

Question: Why do we have a --experimental-policy? #1283

Closed
RedYetiDev opened this issue Apr 17, 2024 · 4 comments
Closed

Question: Why do we have a --experimental-policy? #1283

RedYetiDev opened this issue Apr 17, 2024 · 4 comments

Comments

@RedYetiDev
Copy link
Member

In the NodeJS threat model, it asserts that certain code, including dynamically loaded dependencies, is inherently trusted. However, despite this trust, there exists a permissions policy. Why is such a policy necessary if the code is already deemed trustworthy according to the threat model?

@targos
Copy link
Member

targos commented Apr 18, 2024

What I understood about it is that you trust the code at some point and you make a policy to ensure that in the future you are not running a different (modified, untrusted) version of that initial code.

@RafaelGSS
Copy link
Member

Note that this feature was developed before our threat model. AFAIK it's not a security mitigation for all supply-chain-attack vectors, but a seatbelt. It does work well except for its many edge cases.

@RedYetiDev
Copy link
Member Author

It does work well except for its many edge cases.

IMO If there are any edge cases, then it doesn't really work well, so I agree with nodejs/node#52575's proposal to remove it.

@RafaelGSS
Copy link
Member

Closing in favour of nodejs/node#52575

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants