With this change, seq-forwarder will look for SSL certificates in the local machine certificate store on Windows:
Certificates will be matched according to the hostname that seq-forwarder is listening on, so for example, if listenUri is https://example.com then a certificate with CN=example.com will be matched.
Certificates must be trusted, and must have a private key, or they will be ignored.
Note that the bind-ssl command is obsolete and no longer required, so I've removed it in this PR.
With this change,
seq-forwarderwill look for SSL certificates in the local machine certificate store on Windows:Certificates will be matched according to the hostname that
seq-forwarderis listening on, so for example, iflistenUriishttps://example.comthen a certificate withCN=example.comwill be matched.Certificates must be trusted, and must have a private key, or they will be ignored.
Note that the
bind-sslcommand is obsolete and no longer required, so I've removed it in this PR.