Use SSPI in a Windows context for proxy authentication

[SadarSSI]

Hi,

Following our discussions about NTLM authentication, I took the time to look at how it works between the Windows workstation and the proxy. The answer is the use of Security Support Provider Interface: SSPI.

The browsers like Chrome and MSEdge, for example, transmit the Windows session credentials to the proxy and this works transparently: no user and password to provide to use the proxy.

I looked at how to implement this in RUST because there is a library available (https://docs.rs/sspi/latest/sspi/), and this library does not allow, in its current version, to use the Windows session credentials as browsers do, but requires the domain name, user and password.

To be seen how this library evolves afterwards because it would allow to get rid of the user / password management !