Just a quick update to tell about a new Docker based on the phocean/msf image.
It provides an image for the BeEF framework for XSS browser exploitation (http://beefproject.com/).
I pushed the image on Docker Hub, so that deploying it is now as easy as:
docker pull phocean/msf
It is an automatic build based on the Github repository.
It means that the image is built by Docker, not by me. For this task, they simply have a read access to the Dockerfile on Github.
Thus, you may place in this image the same level of trust than the one you have in Docker (I cannot interfere in the process and mess with the image).
I say it because I am myself reluctant of installing third-party images. While I prefer to rebuild everything from Dockerfiles, I am fine with automatically built images if I am in a hurry and for non sensitive data.
Just a quick note to say that I am very happy about this Metasploit docker image being useful to some people, according to the feedback I got.
And Lenny was kind enough to integrate it into his Linux distro, REMnux, well known among reversing people. He also came up with very good suggestions and helped me to bring some improvements, so many thanks to him.
Don’t miss reading his blog article on how to use the image in REMnux : “Run Metasploit Framework as a Docker Container Without Installation Pains”.
Stay tuned ;-)
I made a few improvements (at least, I think they are) to the metasploit-frameword Dockerfile :
It is all up-to-date in its github repo. I will keep adjusting it, if I feel something is missing.
I hope I did it the right way, let me know what you think!
Managing updates and dependencies of a Metasploit installation have definitely been too much trouble and repetitive.
Instead of keeping reproducing boring installation steps every x months, I decided to build a Dockerfile for once.
I chose Debian for its good compromise between features, stability and lightness. I am aware of the Kali Dockerfile, that I could have used as a base. But:
So, this Debian-based Metasploit container comes with:
You can find it on my github.
If you have any trouble or suggestion on how to improve it, please let me know. Enjoy it and go ahead if you want to fork it!
I just put on my github a few dockerfiles for virtual machines that I frequently use to get some quick work done or to temporary share some data.
Here they are:
I used to use VirtualBox guests, but maintaining them was a hassle (updates, snapshots, disk defragmation and shrinking, etc.).
It makes perfect sense to use Docker just for that, and on top of that it consumes much fewer resources. Starting with the disk usage : all these containers along with their image stands below 1 GB!
The fact that I am using Btrfs as the underlying storage driver is not for nothing: compression is extremely efficient on images!
Note that my Dockerfiles have nothing special, you can actually find others on the Internet (and I was inspired by some).
There are a few differences, however:
While I was playing, I had two things bothering me: