Rikudou_Sage

Shameless advert: Come join lemmings.world! No policing, unless you’re a troll or a bigot.

Oh yeah, let’s wait until they start murdering people to maybe take some action.

The cracks, they don’t remove our protection. The cracks still have all our code in and all our code is executed. There is even more code on top of the cracked code - that is executing on top of our code, and causing even more stuff to be executed. So there is technically no way that the cracked version is faster than the uncracked version. That’s simply a technical fact.

Going by that logic, there’s simply no way that Denuvo does not hinder performance.

RPS: The study you mention showed that having Denuvo software improves revenues at launch, but also showed that a certain point after release - I think it was around three months - it evens out. Do you think publishers should have a policy of eventually removing Denuvo and making that clear to players in their marketing?

Andreas Ullmann: That’s the only point of the study where I’m not totally agreeing.

Well, who would have thunk!

1. For all the mentioned cases, if your firewall blocks incoming packets by default, no one can access it, no matter what is the source of the port being open.

2. You don’t configure it on the docker level, at least if you care about outside connections. If you mean from your local computer to a docker container, by default you cannot connect, unless you expose the port to the system. If you mean from other docker containers, just create your own separate network to run the container in and even docker containers cannot access the ports.

3. I usually use netstat -tulpn, it lists all ports, not only docker, but docker is included. docker ps should also show all exposed ports and their mappings.

In general, all docker containers run on some internal docker network. Either the default or a custom one. The network’s ports don’t interfere with your own, that’s why you can have 20 nginx servers running in a docker container on the same port. When you bind a port in docker, you basically create a bridge from the docker network to your PC’s local network. So now anything that can connect to your PC can also connect to the service. And if you allow connection to the port from outside the network, it will work as well. Note that port forwarding on your router must be set up.

So in conclusion, to actually make a service running in docker visible to the public internet, you need to do quite a few steps!

• bind a port to your local host
• have your local firewall allow connection to the port
• have your router set up to forward connections on the port to your machine

On Linux, local firewall is usually disabled by default, but the other two steps require you to actively change the default config. And you mention that all incoming traffic is dropped using UFW, so all three parts should be covered.

I did this with a suitcase lock once, luckily only 3 digits. The code was 587. I remembered the code at around 540.

46.6˚C in normal units.