opt() :: ranch_tcp:opt() | ssl_opt()
ranch_ssl - SSL transport
The module ranch_ssl
implements an SSL Ranch transport.
The module ranch_ssl
implements the interface defined by ranch_transport(3).
opt() :: ranch_tcp:opt() | ssl_opt()
Listen options.
The TCP options are defined in ranch_tcp(3).
opts() :: [opt()]
List of listen options.
ssl_opt() = {alpn_preferred_protocols, [binary()]} | {beast_mitigation, one_n_minus_one | zero_n | disabled} | {cacertfile, string()} | {cacerts, [public_key:der_encoded()]} | {cert, public_key:der_encoded()} | {certfile, string()} | {ciphers, [ssl:erl_cipher_suite()] | string()} | {client_renegotiation, boolean()} | {crl_cache, {module(), {internal | any(), list()}}} | {crl_check, boolean() | peer | best_effort} | {depth, 0..255} | {dh, public_key:der_encoded()} | {dhfile, string()} | {fail_if_no_peer_cert, boolean()} | {hibernate_after, integer() | undefined} | {honor_cipher_order, boolean()} | {key, {'RSAPrivateKey' | 'DSAPrivateKey' | 'PrivateKeyInfo', public_key:der_encoded()}} | {keyfile, string()} | {log_alert, boolean()} | {next_protocols_advertised, [binary()]} | {padding_check, boolean()} | {partial_chain, fun(([public_key:der_encoded()]) -> {trusted_ca, public_key:der_encoded()} | unknown_ca)} | {password, string()} | {psk_identity, string()} | {reuse_session, fun()} | {reuse_sessions, boolean()} | {secure_renegotiate, boolean()} | {signature_algs, [{atom(), atom()}]} | {sni_fun, fun()} | {sni_hosts, [{string(), ssl_opt()}]} | {user_lookup_fun, {fun(), any()}} | {v2_hello_compatible, boolean()} | {verify, ssl:verify_type()} | {verify_fun, {fun(), any()}} | {versions, [atom()]}
SSL-specific listen options.
Specifying a certificate is mandatory, either through the cert
or certfile
option, or by configuring SNI. None of the other options are required.
The default value is given next to the option name:
Perform Application-Layer Protocol Negotiation with the given list of preferred protocols.
Change the BEAST mitigation strategy for SSL-3.0 and TLS-1.0 to interoperate with legacy software.
Path to PEM encoded trusted certificates file used to verify peer certificates.
List of DER encoded trusted certificates.
DER encoded user certificate.
Path to the PEM encoded user certificate file. May also contain the private key.
List of ciphers that clients are allowed to use.
Whether to allow client-initiated renegotiation.
Customize the module used to cache Certificate Revocation Lists.
Whether to perform CRL check on all certificates in the chain during validation.
Maximum of intermediate certificates allowed in the certification path.
DER encoded Diffie-Hellman parameters.
Path to the PEM encoded Diffie-Hellman parameters file.
Whether to refuse the connection if the client sends an empty certificate.
Time in ms after which SSL socket processes go into hibernation to reduce memory usage.
If true, use the server's preference for cipher selection. If false, use the client's preference.
DER encoded user private key.
Path to the PEM encoded private key file, if different from the certfile.
If false, error reports will not be displayed.
List of protocols to send to the client if it supports the Next Protocol extension.
Allow disabling the block cipher padding check for TLS-1.0 to be able to interoperate with legacy software.
Claim an intermediate CA in the chain as trusted.
Password to the private key file, if password protected.
Provide the given PSK identity hint to the client during the handshake.
Custom policy to decide whether a session should be reused.
Whether to allow session reuse.
Whether to reject renegotiation attempts that do not conform to RFC5746.
The TLS signature algorithm extension may be used, from TLS 1.2, to negotiate which signature algorithm to use during the TLS handshake.
Function called when the client requests a host using Server Name Indication. Returns options to apply.
Options to apply for the host that matches what the client requested with Server Name Indication.
Function called to determine the shared secret when using PSK, or provide parameters when using SRP.
Accept clients that send hello messages in SSL-2.0 format while offering supported SSL/TLS versions.
Use verify_peer
to request a certificate from the client.
Custom policy to decide whether a client certificate is valid.
TLS protocol versions that will be supported.
Note that the client will not send a certificate unless the value for the verify
option is set to verify_peer
. This means that fail_if_no_peer_cert
only applies when combined with the verify
option. The verify_fun
option allows greater control over the client certificate validation.
The options sni_fun
and sni_hosts
are mutually exclusive.
ranch(7), ranch_transport(3), ranch_tcp(3), ssl(3)
Donate to Loïc Hoguin because his work on Cowboy, Ranch, Gun and Erlang.mk is fantastic:
Recurring payment options are also available via BountySource. These funds are used to cover the recurring expenses like dedicated servers or domain names.