-
Notifications
You must be signed in to change notification settings - Fork 30k
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
--experimental-permission
breaks REPL
#48884
Comments
Hi, thanks for reporting it. I'm aware of this behaviour. |
Question is: should we make the internal calls to the inspector possible/privileged, or do like when the inspector is unavailable (this would just be a new condition in node/lib/internal/util/inspector.js Lines 48 to 49 in a0f3ed8
|
I believe REPL shouldn't be available when the permission model is enabled. Please let me know if I'm wrong, but the REPL can create a new V8 isolate and bypass any permission in several ways. If we start supporting REPL, it would mean that we need to cover all those cases. |
Can you elaborate? |
Basically, the same as 34d92ed fixes. I don't have a reproducible example because I'm not sure if that's possible. I'm just wondering if REPL can create a new V8 isolate, it means it could create without the experimental permission rules, right? Anyway, I created the #48920. |
PR-URL: #48920 Fixes: #48884 Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
PR-URL: nodejs#48920 Fixes: nodejs#48884 Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
PR-URL: nodejs#48920 Fixes: nodejs#48884 Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
PR-URL: nodejs#48920 Fixes: nodejs#48884 Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
PR-URL: nodejs#48920 Fixes: nodejs#48884 Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
PR-URL: nodejs#48920 Fixes: nodejs#48884 Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
PR-URL: nodejs#48920 Fixes: nodejs#48884 Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
PR-URL: nodejs#48920 Fixes: nodejs#48884 Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
PR-URL: #48920 Fixes: #48884 Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
PR-URL: #48920 Fixes: #48884 Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
Version
20.5.0
Platform
any
Subsystem
permission model
What steps will reproduce the bug?
Open a REPL and start typing:
How often does it reproduce? Is there a required condition?
Always.
What is the expected behavior? Why is that the expected behavior?
No error.
What do you see instead?
Fatal error:
Additional information
Likely side effect of 34d92ed.
The text was updated successfully, but these errors were encountered: