Closed PSLLSP closed 4 months ago
The scanner has been designed primarily for local scanning of clients. This means a user fires up the scanner and follows up with the SSH client to test it on the same machine. In this scenario, it is unnecessary and may not be desirable to bind to 0.0.0.0 due to port conflicts or firewall rules. If the scanner is being used over the network, one can specify 0.0.0.0 explicitly as the bind address (as done in your workarounds). So, I do think that the current behavior is more in line with the overall design goals of the scanner, which is why I will keep this behavior for now.
When no host is specified in listen mode, scanner is binded to the local interface, 127.0.0.1. Why not 0.0.0.0?
Workarround (IPv4):
Workarround (IPv6):