[Bug]: shim server should only be bound to localhost interface

[colinjc]

Steps to reproduce

When using ssh instances we can curl the shim server from a public ip

Actual behaviour

No response

Expected behaviour

No response

dstack version

0.19.8

Server logs

Additional information

No response

[jvstme]

SSH fleet instances should have a firewall to protect the shim port and any other ports that can be bound to by users' runs (most runs can't bind to ports on the host, but distributed tasks can). Only SSH traffic should be allowed from external networks. I will mention this in the docs.

As an extra security measure, however, we should still bind shim to localhost only.

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 14 days since being marked as stale. Please reopen the issue if it is still relevant.