CLI Flag to Disable Headless Mode's Chromium Sandbox #3878
Assignees
Labels
Status: Completed
Nothing further to be done with this issue. Awaiting to be closed.
Type: Enhancement
Most issues will probably ask for additions or changes.
Milestone
Comments
ErikOwen
added
the
Type: Enhancement
|
@ErikOwen I've updated the issue to add flag option, similar to what we have in Katana, that lets the user define any chrome related options as needed. |
4 tasks
ehsandeep
added
the
Status: Completed
|
@ErikOwen this is now possible with latest release - https://github.com/projectdiscovery/nuclei/releases/tag/v2.9.10 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please describe your feature request:
It would be nice to have a CLI flag to disable the Chromium sandbox that is configured when running headless templates. Right now this logic is what determines if chromium's sandbox is disabled or not.
-ho, -headless-options string[] start headless chrome with additional optionsDescribe the use case of this feature:
When running on AWS Fargate I want to be able to use Nuclei as a non-root user and still be able to launch chromium. I wish to do this by running Nuclei as a non-root user and passing in a flag to Nuclei to instruct Nuclei to disable chromium's sandbox functionality. Right now AWS Fargate does not allow containers to run in privileged mode, so the
--no-sandboxflag must be passed to chromium for it to be able to run on AWS Fargate (see more information here). So currently the only way to run nuclei's headless templates in AWS Fargate is by running Nuclei as root, which is not ideal.The text was updated successfully, but these errors were encountered: