Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to use SSL under Linux (Debian)? #57

Closed
Einhornyordle opened this issue May 15, 2021 · 1 comment
Closed

How to use SSL under Linux (Debian)? #57

Einhornyordle opened this issue May 15, 2021 · 1 comment

Comments

@Einhornyordle
Copy link

I created a simple WatsonWsServer and set the ssl bool to true but how do i specify the ssl certificate to use under debian (since there is no netsh command available)?

@jchristn
Copy link
Owner

Hi @Einhornyordle I unfortunately don't have a good example for you. I'd suggest looking into ways of binding HttpListener with a certificate in either Mono or .NET Core Linux environments. The links I'm seeing don't look too promising in terms of native SSL support with HttpListener (which WatsonWebsocket is based on). For example:

karelz commented on Oct 22, 2018 • 
@martin-frydl I think we're running in circles here.
.NET Core does not support SSL in HttpListener on Linux. Using Reflection to hack-enable features is unsupported and we want to DISCOURAGE anyone from doing that. Fixing bugs on such code paths proactively is encouragement and goes against our goals. Hence, the priority is extremely low. We did not close the issue right away just because it will be needed one day for full SSL support in HttpListener on Linux (#19752).

This may or may not be helpful (it is for Mono environments, but may work for .NET Core): http://joshua.perina.com/geo/post/using-ssl-https-with-mono-httplistener

If not, you may have to run your code behind something like nginx.

Would you mind trying the link and let us know how it goes?

Repository owner locked and limited conversation to collaborators May 16, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants