Dockerize this toolkit about fsociety HOT 14 CLOSED

I will work on this

from fsociety.

Hey @jdrago999 I honestly don't know enough about docker, would you be able to make a PR that does this?

Yes I would be happy to push this forward, working with other projects' maintainers as necessary.

from fsociety.

@jdrago999 thank you

from fsociety.

Ok @jdrago999 I added a Dockerfile, let me know if it works for you

from fsociety.

Hey @thehappydinoa I was thinking about it a different way. Usually a container is used for a single tool -- so instead of running pip install beautifulsoup4 && pip install requests in the host OS just so we can install https://github.com/AeonDave/doork it would be better to make sure that doork itself has a properly maintained Dockerfile and a working fsociety/doork Docker image on https://hub.docker.com/

Also, what happens if doork changes and now it requires a different version of requests or beautifulsoup or there are some other libraries required (eg: libcrypto++-dev or libxml2-dev) and simply running pip install beautifulsoup4 && pip install requests no longer works?

By pushing the responsibility of dependency management upstream into Docker containers, we gain the ability to have more reliable tools and reduce overall effort to make things work.

If the maintainers of the various upstream tools (like doork) want to participate in this effort, that would be great.

from fsociety.

Hey @jdrago999 I honestly don't know enough about docker, would you be able to make a PR that does this?

from fsociety.

@jdrago999 I might be able to help on this , But could you explain what are you planning to do ? Are we talking about a separate image for each tool and this case we will have a tool per container ?

from fsociety.

fyi trying out the docker commands I get the following error
error.txt

edit: I am on a mac

from fsociety.

@mostafahussein:

Are we talking about a separate image for each tool and this case we will have a tool per container?

Yes precisely. And yes I realize that could be a lot of work, but I hope that having each of these tools running within an environment well-suited to them will alleviate the kinds of problems we run into when one tool has requirements that don't play well with another tool's requirements.

from fsociety.

I think that will be a maintenance nightmare, putting all the tools in one docker container makes more sense to me, then I can simply mount my ssh keys as an external volume, and any data partitions I want and then run the docker image and attach to it.

from fsociety.

Hi all thank you so much for all the ideas, I am honestly not the best with docker so if you guys could make PRs as things go on that would be great.

from fsociety.

@Isanderthul I am unable to view that file, could you create a new issue?

from fsociety.

new issue made #12

from fsociety.

here you go #13

from fsociety.