NetworkDiscoverer has a bug in which a service can be registered for IPAddress.Loopback or IPAddress.IPv6Loopback and requests for that service from other machines over non-loopback interfaces will trigger a response for the previously registered loopback service.
This is obviously bullshit and should be changed to prevent loopback services to be discovered over non-loopback interfaces.
However I am unsure if anything more sophisticated could / should be done here (if a service is bound to address X and we receive a request for that service through an interface with address Y [where X != Y], should we then not send a response as well?).
Kittyfisto
commented
5 years ago
NetworkDiscoverer has a bug in which a service can be registered for IPAddress.Loopback or IPAddress.IPv6Loopback and requests for that service from other machines over non-loopback interfaces will trigger a response for the previously registered loopback service.
This is obviously bullshit and should be changed to prevent loopback services to be discovered over non-loopback interfaces.
However I am unsure if anything more sophisticated could / should be done here (if a service is bound to address X and we receive a request for that service through an interface with address Y [where X != Y], should we then not send a response as well?).