Closed RMerl closed 4 years ago
Thanks, will have a look next week when i have more time.
That fix appear to be incomplete. While it at least reduces the number of sockets, connecting from an unprotected WAN still seems to succeed. I suppose the socket code will need to be amended to only bind to the interface's IP address, and not to 0.0.0.0.
By default wsdd2 binds to all available interfaces. In a router's case this means it would also bind to the WAN interface, which is a security risk. This allows to instruct wsdd2 to which specific interface to bind to.