-
Notifications
You must be signed in to change notification settings - Fork 428
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
Expose more SSL options in cowboy #888
Comments
What ranch version do you have in mind? |
I believe sni_hosts was added in ranch 1.2.0, meaning that it's pulled in by cowboy in master only - it'll probably make it into 2.0 but it's not in any of their betas yet... |
While on this topic, would you consider a patch that treats SSL parameters as opaque and just passes them all the way down to ranch? That's pretty much what cowboy does anyway. I guess one could still keep the currently defined set of common http/https options explicit (i.e., ip, port, max_connections and max_acceptors) for backwards compatibility. I.e., something like the following:
|
Yes, that looks cool :) Waiting for the patch :) |
You can force rebar to download ranch 1.2.0 by specifying it in deps before cowboy. The question is , does cowboy 1.0.4 work with ranch 1.2.0? Hopefully our tests will show that. |
I made a separate pull request for those changes. I haven't really had a chance to test out the new ranch version so I can't really comment on that. |
Many thanks for the merge! |
The ranch version pulled in by cowboy dependency is quite outdated and does not expose a number of useful ssl parameters (dhfile being one of the more critical ones). Issue esl#888
The ranch version pulled in by cowboy dependency is quite outdated and does not expose a number of useful ssl parameters (dhfile being one of the more critical ones). Issue #888
MongooseIM version: current master
Installed from: source
Erlang/OTP version: OTP 18
There are a bunch of potentially useful SSL options that are not exposed by cowboy config. The ones that seem particularly useful/important are "cacerfile" (needed to send the full certificate chain to the client, which is pretty much required if your cert is signed by an intermediate CA), "ciphers" - allows to limit the set of supported ciphers and "versions" - limits SSL/TLS versions supported by the server.
BTW, it'd be potentially nice to upgrade to a newer ranch version - it now exposes "sni_hosts" option, which could be really useful for environments serving more than one domain.
The text was updated successfully, but these errors were encountered: