-
Notifications
You must be signed in to change notification settings - Fork 80
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
ssl_key_passphrase
does not work
#364
Comments
I am also experiencing this problem in Version 7.3.0 in the official docker container. The same error exists in the HTTP input plugin, which also is unable to decrypt passphrase protected PKCS8 keys. |
@ph @robbavey This is a pretty far reaching problem when using encrypted private keys, which should be preferred particularly with the function of the logstash keystore. My understanding is that it's looking at the first line of the file to determine if it's pkcs8, if it doesn't see the right header, it throws it away. I'm also noticing that bug occurs on other input plugins like If there is any additional information to add to troubleshooting, please ask me to provide. |
the underlying error for this one is very probably the same as identified at #391 (comment):
(the error message/type gets a bit lost with Netty exception handling) the problem is standard JDK libraries have issues reading PKCS8 encrypted (PEM) keys generated by |
This still does not work in version 7.8. I just wasted a couple of hours trying to get my encrypted certificate to work. If you are not going to fix it then please al least put a note in the documentation that it doesn't work. |
Does anyone have ssl working between filebeat and logstash? Ihave followed all the documentation and posts with no luck. I know my certs and keys are working between logstash and Elasticsearch. |
It works for me if I use a certificate that doesn't have a password, so is not encrypted. |
Still not working for me, getting an error in the elogstash log when I use the ssl config below: curl -XGET -u elastic:******** --cacert /etc/logstash/ca.crt --cert /etc/logstash/siem-logstash-01.crt --key /etc/logstash/siem-logstash-01.key 'https://siem-elasticsearch-01:9200/_cluster/health?pretty' Error in logstash log: |
I had similar issue , unable to use passhprase protected key on beats. Service not starts since unable to read the key. In this case key header starts with ""-----BEGIN RSA PRIVATE KEY-----Proc-Type: 4,ENCRYPTED" and it works. When I tried to use pkcs8 format that starts with "-----BEGIN ENCRYPTED PRIVATE KEY-----" it didn't worked for me. |
The
beat_input_ssl_key_passphrase
is the variable name I used to store the password securely in the logstash keystore. I also tried adding the password in plaintext. Logstash fails to start with the error output here: https://pastebin.com/BdsqiWcHThere are other people that seem to have the same issue.
The text was updated successfully, but these errors were encountered: