New answers tagged

1

Use a debugger! Dynamic analysis is an exceptional way to learn how a "product" works. What do you mean with "cracking a software which is installed with Docker on Linux"? It depends on which technology make that software run on the Linux OS. Is it an ELF? It is a Java JAR? A shell script? Basically, reverse engineering is about ...


13

When you're using rootless Docker/Podman, the risks of allowing users to bind ports < 1024, generally depend on what else is happening on the system. TBH the old restriction on low ports doesn't really apply that much any more, as loads of sensitive ports are over 1024 (e.g. Docker itself which will default to listening on 2375 or 2376). There could be a ...


12

It depends on your system. If it's a multi-user system with multiple users able to run docker, you may fall victim to a race attack, where a malicious docker container is started when your legitimate docker is restarting for some reason. However, it's worth noting that becoming root if you can access docker is generally trivial, and securing your docker ...


2

In practice I haven't seen that often. As long as the traffic is secure without encryption between the reverse proxy (nginx) and the application (e.g. on the same hardware or safe network); and it is OK for you that the nginx instance handles all your network certificates nginx would handle HTTPS and proxy_pass the rest upwards. This has advantages of ...


Top 50 recent answers are included