Lockdown your Dockerized build environments --- Because privileged mode is insecure, you should restrict your CI/CD environments to known users and projects. If this isn't feasible, then instead of using Docker, you could try using a standalone image builder like Buildah to eliminate the risk. Alternatively, configuring rootless Docker-in-Docker can mitigate some --- but not all --- of the security concerns... - Source: dev.to / about 1 month ago

In my experience, not using docker to build docker images is a good idea. E.g. buildah[0] with chroot isolation can build images in a GitLab pipeline, where docker would fail. It can still use the same Dockerfile though. If you want to get rid of your Dockerfiles anyway, nix can also build docker images[1] with all the added benefits of nix (reproducibility, efficient building and caching, automatic layering,... - Source: Hacker News / 8 months ago

Buildah: This lightweight, open-source command-line tool for building and managing container images. It is an efficient alternative to Docker. With Buildah, you can build images in various ways, including using a Dockerfile, a podmanfile or by running commands in a container. Buildah is a flexible, secure and powerful tool for building container images. - Source: dev.to / about 1 year ago

When I saw the title I thought it was going to be about `buildah` [1][2] Which allows you to create images using the command line to build them up step-by-step. [1] https://buildah.io/. - Source: Hacker News / over 1 year ago

Buildah is a "tool that facilitates building OCI images" of Containers. If it is not installed, podman system migrate will print out the warning:. - Source: dev.to / over 1 year ago

Https://app.any.run/ should be enough for most of the cases. If you have packed/encrypted sample (like EMP.dll from Empress), you can't do anything. Source: about 1 year ago

If you open it on https://app.any.run it will show you the outbound connections it makes. If you're responsible for such things, you could then block this on your web proxy/firewall/whatever. Source: about 1 year ago

Hello! Try this https://app.any.run/. Source: over 1 year ago

Does anyone have an account at app.any.run to have more analysis about their file? Source: over 1 year ago

App.any.run was probably the most useful thing in getting to understand how malware works, its basically an sandbox where it shows you all actions, changes, modifications and network connections done by any executable, including any malware, you can begin by analyzing this piece of Redline Stealer. Source: over 1 year ago