-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Kafka output and SSL/TLS #1126
Comments
Seems that this is the issue I'm having, IBM/sarama#643 |
Damn politics! http://docs.oracle.com/javase/8/docs/technotes/guides/security/SunProviders.html#importlimits So OpenJDK cant support higher ciphers |
It goes deeper |
interesting, thanks for digging @elvarb, what's the conclusion? Don't run Kafka with Oracle Java 8? |
By default using Confluent 2.0 with Kafka 0.9 and the latest OpenJDK these ciphers are available. Found by using sslscan
From the Golang docs these are available. https://golang.org/pkg/crypto/tls/
Still trying to get the extra ciphers from Oracle in. |
The extra ciphers probably only work with the Oracle JDK http://armoredbarista.blogspot.is/2013/10/how-to-use-ecc-with-openjdk.html |
I have been beating my head against the wall for the last days, no matter what I do I can not get Kafka to allow for other ciphers. Can't spend more time on this, but my results are that at least on Centos you can not use SSL when using Kafka from Go programs. |
Using any other provider than some default one Kafka uses is impossible, always says provider not found. For example this
|
Created a ticket with the Kafka project https://issues.apache.org/jira/browse/KAFKA-3647 |
Solution found, When you create the keystore use -keyalg RSA, then you will get the right ciphers. |
I have set up SSL with Kafka 0.9, created the CA, certs and keys for 1/4 Kafka nodes. Created the Client cert/key and tested it from Logstash 5.0 beta and that works.
When using Telegraf I'm getting this error
And this is my Telegraf config
The main difference here from Logstash is that I'm using the raw pem and key files here but with Logstash I'm using JKS stores created from the raw pem and key files.
The text was updated successfully, but these errors were encountered: