-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[TLS] Fluentd does not accept certificates containing CRLF instead of LF #2889
Comments
pbudner
added a commit
to pbudner/fluentd
that referenced
this issue
Mar 16, 2020
…ogging when parsing certificates
pbudner
added a commit
to pbudner/fluentd
that referenced
this issue
Mar 16, 2020
…ogging when parsing certificates Signed-off-by: Pascal Budner <mail@pascalbudner.de>
pbudner
added a commit
to pbudner/fluentd
that referenced
this issue
Mar 16, 2020
…ogging when parsing certificates Signed-off-by: Pascal Budner <mail@pascalbudner.de>
pbudner
added a commit
to pbudner/fluentd
that referenced
this issue
Mar 16, 2020
…ogging when parsing certificates Signed-off-by: Pascal Budner <mail@pascalbudner.de>
repeatedly
added a commit
that referenced
this issue
Mar 17, 2020
Fixes #2889 by supporting CRLF and LF X.509 certificates
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Enabling TLS transport using a valid X.509 certificate that contains CRLF instead of LF leads to an unexpected behavior. Fluentd is not able to parse the valid certificate and refuses to do TLS handshakes.
To Reproduce
Specify a forward input using TLS that points to a certificate containing CRLF instead of LF.
Expected behavior
Fluentd should warn if it could not parse and find a valid certificate in the given cert_path content. Also Fluentd should be able to handle certificates that contain CRLF instead of LF.
Your Environment
fluentd 1.9.3
NAME="Amazon Linux" VERSION="2" ID="amzn" ID_LIKE="centos rhel fedora" VERSION_ID="2" PRETTY_NAME="Amazon Linux 2" ANSI_COLOR="0;33" CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2" HOME_URL="https://amazonlinux.com/"
4.14.171-136.231.amzn2.x86_64
Your Configuration
Your Error Log
Additional context
nothing to add here
The text was updated successfully, but these errors were encountered: