-
Notifications
You must be signed in to change notification settings - Fork 1k
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
SSL Configuration Fails Unless Fully Configured #3594
Comments
yes, that sounds right to me - can we setup a reproduction spec for this? Because if what you're saying is true then Akka.Remote should always be catching fire whenever anyone uses it without explicitly setting up SSL, no? |
No, only if they've explicitly setup invalid SSL but regardless of whether 'enable-ssl' is true or false. I haven't revisited this since I first reported it, I'll have a look and see if I can produce a spec. |
Hello. Any update on it? It is an issue for us as well. |
@aminchenkov no, we haven't done any work on this as I haven't heard much about this issue in 4 years. This should be an easy fix though - just need to disable SSL section validation in Akka.Remote unless it's loaded. PR's welcome. |
@Aaronontheweb , could you review #6038? |
That PR looks good. We'll include this fix inside the 1.4.40 release. |
@Aaronontheweb , do you know release date? |
@Aaronontheweb , thank you! |
Fixed in 1.4.40. |
When setting up SSL configuration I have to set valid path, password and flags properties even when enable-ssl is set to false.
Which Akka.Net version you are using
On which platform you are using Akka.Net
A list of steps to reproduce the issue. Or an gist or github repo which can be easily used to reproduce your case.
I would expect to be able to provide 'invalid' sample ssl configuration while 'enable-ssl' is set to false, the ssl configuration details should not be validated unless 'enable-ssl' is set to true.
N.B. the documentation says the default flags should be: "default-flag-set", while it appears the actual valid value is: "default-key-set".
The text was updated successfully, but these errors were encountered: