-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Allow wildcards in --allow-net allow lists. #6532
Comments
Just to clarify a nuance here: |
Yes you are right. |
This especially! |
Ran into this just now with the aws sdk. Was wanting to limit to something like |
Hi @ry this issue has been open for 2 years and we haven't heard any positive response about it, anything going on with this? |
There is no movement on this front whatsoever. I will raise this topic on the next design meeting. |
Okay, thanks for your concern. |
While this is not a priority for the core team, we would be happy to accept a PR that implements wildcard matching for |
Am I on base in thinking that the changes would be in this permissions.rs file, specifically UnaryPermission<NetDescriptor>'s 3 "check" methods (check, check_url, and check_all)? I don't really know Rust (or how to read it...) but that's where I got to after some code tracing. |
It will be good to allow wildcards in the
--allow-net
allow lists.For example, this code throws errors:
deno run --allow-net=facebook.com server.js
Because https://facebook.com redirects to https://www.facebook.com
This should be possible to run it;
deno run --allow-net=*.facebook.com server.js
Port based wildcards might also be good. For example
https only
deno run --allow-net=https://* server.js
or
deno run --allow-net=*/**:443 server.js
The text was updated successfully, but these errors were encountered: