Established Dockerfile for creating container for powerpwn #82
Conversation
Improve naming, development environment and intro tests
re-org dirs to allow cnn integration
Feature/windows puppeteer support copilot hunter
…t-copilot365 Launch puppeteer browser with windows default location for chrome.exe…
install prereqs on the devcontainer
task/i80 - container fix for copilot-hunter
Add additional copilot studio hunter directories to package data
|
---no-sandbox is not the most secure idea, but it seems like the risk would be based on visiting a malicious site. Since we are not building the URLs based on user input, it seems safe to do this. Best practice would be to figure out how to build and run the container as a user instead of root. This would require the python package for powerpwn to be installed in that user's home area instead of the default location. seems like more effort than worth at the moment |
…om/mbrg/power-pwn into feature/anonymous_powerpages_check
…om/mbrg/power-pwn into feature/anonymous_powerpages_check
power pages module
…ectory for easy download by inexperienced users
I'd be worried to pick and up run a "run security tool" off the internet with root prv |
Created a Dockerfile which mimics the devcontainer setup. We should be able to build our own container now, distribute it and allow folks to run powerpwn from the container. Probably would be good to setup an action to publish new versions of the container to docker hub or somewhere else. Also, suggest figuring out how to not need to install from sources (mostly a problem with the puppeteer stuff I think. Had to add the --no-sandbox so this would run properly in a container that is running as root.