-
Since upgrading to vector 0.32 with bundled openssl from v1.1 to v3.0, it starts to refuse weak encryption algorithms for safety reasons (that's good). Specifically we are trying to sink messages to a tls-enabled kafka, which is unfortunately self-signed with weak key, thus, vector fails to verify certification during ssl handshake. Upgrading sever side cert is not an option at the moment, so we are trying to figure out a way to allow weak key in vector. So could there be workaround to allow weak key for ssl to work? (Yes, we understand compromised security risks.) Probably by tweaking openssl config outlined here at librdkafka? Which I did try but it seems not work yet. SetupMy setup is using docker image ( [sources.bind]
type = 'stdin'
[transforms.bind_decode]
type = "remap"
inputs = ["bind"]
source = '''
. = parse_json!(.message)
'''
[sinks.bind_next_kafka]
type = "kafka"
inputs = [ "bind_decode" ]
bootstrap_servers = "my-broker:9093"
topic = "user-event"
sasl.enabled = true
sasl.mechanism = "SCRAM-SHA-256"
sasl.username = "redacted"
sasl.password = "redacted"
encoding.codec = "json"
tls.enabled = true
tls.ca_file = "/etc/vector/my.pem" vector fails to do ssl handshake during healthcheck.
DebugWith the vector container, there is openssl v3 bundled in. Using it to test revealed that
Options triedI tried to follow confluentinc/librdkafka#4204, by appending config to openssl conf
run |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Okay, I made openssl to work by using this config (have to downgrade sec level to zero):
openssl now verifies ok,
By explicitly specify openssl conf, vector works now:
|
Beta Was this translation helpful? Give feedback.
Okay, I made openssl to work by using this config (have to downgrade sec level to zero):
openssl now verifies ok,
but vector still reports error,By explicitly specify openssl …