On Windows, a socket binding a port without setting SO_EXCLUSIVEADDRUSE can be hijacked by other applications that set the SO_REUSEADDR flag. See the Microsoft documentation "Using SO_REUSEADDR and SO_EXCLUSIVEADDRUSE".
Unfortunately it looks like there is currently no easy way to set the SO_EXCLUSIVEADDRUSE option in Windows (e.g. rust-lang/rfcs#861), but because of the security impact I think it would be a very useful addition to this crate. I'm open to suggestions on how to implement it in an idiomatic way.
On Windows, a socket binding a port without setting
SO_EXCLUSIVEADDRUSEcan be hijacked by other applications that set theSO_REUSEADDRflag. See the Microsoft documentation "Using SO_REUSEADDR and SO_EXCLUSIVEADDRUSE".Unfortunately it looks like there is currently no easy way to set the
SO_EXCLUSIVEADDRUSEoption in Windows (e.g. rust-lang/rfcs#861), but because of the security impact I think it would be a very useful addition to this crate. I'm open to suggestions on how to implement it in an idiomatic way.