You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Really like the idea of the extension! What I would love to see is some more configuration options, such as:
Independent TLS settings for the TCP or TLS listener (e.g. no TLS there, just a TCP listener) and connection (e.g. then use TLS to connect to the server)
Client certificate support to the server
The main reason is that it is sometimes easy to control the client software, reconfigure it to not use TLS (and therefore we don't have the wrong-certificate issues), but not control the server-side. Also if a client certificate is involved, we would need to use that when connecting to the server.
That would be really nice
The text was updated successfully, but these errors were encountered:
Sorry... for the delayed reponse... i should be better at monitoring these issues.
I think these are great features. The first bullet point should not be to difficult to add.. The second will be a bit more involved. I'll keep you posted on the progress.
Really like the idea of the extension! What I would love to see is some more configuration options, such as:
The main reason is that it is sometimes easy to control the client software, reconfigure it to not use TLS (and therefore we don't have the wrong-certificate issues), but not control the server-side. Also if a client certificate is involved, we would need to use that when connecting to the server.
That would be really nice
The text was updated successfully, but these errors were encountered: