Open sedinin opened 5 months ago
One can provide e.g. {tls_options, [{verify, verify_none}]} to configuration to avoid problem introduced in erlang 26 (default verify is verify_peer now).
{tls_options, [{verify, verify_none}]}
verify
verify_peer
Can you not just add the tls options to sockoptions manually?
What do you mean by "manually"? I do it almost the same way its done in do_STARTTLS/2, by retrieving from configuration.
One can provide e.g.
{tls_options, [{verify, verify_none}]}
to configuration to avoid problem introduced in erlang 26 (defaultverify
isverify_peer
now).