The default `ssl.endpoint.identification.algorithm` is `null` which is not a secure default (man in the middle attacks are possible).
We should probably use `https` instead. A more conservative alternative would be to update the documentation instead of changing the default.
A paper on the topic (thanks to Ryan Pridgeon for the reference): http://www.cs.utexas.edu/~shmat/shmat_ccs12.pdf
- is related to
KAFKA-3667 Improve Section 7.2 Encryption and Authentication using SSL to include proper hostname verification configuration
- links to
- mentioned in