You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have tls.verify false in FLB configs, which will probably eventually get us a security warning.
As part of this change I tried to change it to true, but this didn't work: #78
Mountebank works building cert at container build time.
Trying to get Fluent Bit to use the cert does not:
[2023/06/22 22:45:59] [error] [tls] crt_file '/cert/mb-csr.pem' 336445449: error:0909006C:PEM routines:get_name:no start line
Despite this error it is formatted properly:
bash-5.2# cat mb-csr.pem
-----BEGIN CERTIFICATE REQUEST-----
So we will keep tls.verify false for now.
The internet suggests that some newline formatting might be the problem, since everything is on linux and there's a single newline between the header and the actual cert, I think that can't be the issue.
The text was updated successfully, but these errors were encountered:
Currently we have
tls.verify false
in FLB configs, which will probably eventually get us a security warning.As part of this change I tried to change it to true, but this didn't work: #78
Mountebank works building cert at container build time.
Trying to get Fluent Bit to use the cert does not:
[2023/06/22 22:45:59] [error] [tls] crt_file '/cert/mb-csr.pem' 336445449: error:0909006C:PEM routines:get_name:no start line
Despite this error it is formatted properly:
bash-5.2# cat mb-csr.pem
-----BEGIN CERTIFICATE REQUEST-----
So we will keep tls.verify false for now.
The internet suggests that some newline formatting might be the problem, since everything is on linux and there's a single newline between the header and the actual cert, I think that can't be the issue.
The text was updated successfully, but these errors were encountered: