New answers tagged


An application running in a standard Docker container as a non-root user is essentially just a non-privileged process running on the host, with additional restrictions applied to it. Firstly, the application will reside within its own set of namespaces (e.g. mount, net) restricting it's view of the host's resources. Then assuming a standard Docker ...


firejail command line utility depending on apparmor of SeLinux apt install firejail firejail --whitelist=~/Chroot bash


You are looking at the wrong problem. Handling the file is not an issue. You can save it in the filesystem if you want. You just need to treat is as data. A database blob, a filesystem entry, an in-memory stream. All of those should work. From Eicar to NotPetya, they are just bytes. The point where you need to be careful is where programs start processing ...


I had the same question and ran into the same scary-sounding answers/comments here on stackexchange. After reading the article linked in another answer, and reading all the apparently-relevant answers here on stackexchange, I think I have made sense of the issue. The problem seems to be that creating an isolated environment involves cloning a "...

Top 50 recent answers are included