On 03/10/2017 4:52 PM, Jesse Phillips wrote:
I'm pretty sure this isn't possible, but maybe someone understands
Windows better.
Windows provides a means no bind a certificate to a port using
netsh.exe. This means (at least for standard Windows networking calls)
connections to that port will be given the bound cert.
The Vibe.d documents state that a Certificate chain and key needs to be
provided. I'm pretty sure that the port binding requires very specific
Network API calls, possible .NET only. Can any confirm or deny?
Perhaps you could reference the command (aka the args with an example)?
Otherwise, its a lot harder to figure out what it is doing under the hood.
