Is there any way to influence hash and cipher selection within ejabberd for c2s and s2s (something roughly comparable to SSLCipherSuite in apache)?
What ciphers and hashes will ejabberd use in the default configuration?
Is there any way to log the ciphers/hashes used in s2s to the log file?
I hope someone could provide some insights here...
Thanks!
answering my own question:
answering my own question: there is no way to influence cipher or hash selection within ejabberd configuration. See for example this Debian security update: (ejabberd -- insecure SSL usage) which backports upstream changes regarding cipher selection from 2.1.12.