Tags: logstash-plugins/logstash-input-tcp
Tags
Standardize and add SSL settings (#213) This commit reviewed and deprecated the following SSL settings to comply with Logstash's naming convention: - ssl_enable in favor of ssl_enabled - ssl_cert in favor of ssl_certificate - ssl_verify in favor of ssl_client_authentication when mode is server - ssl_verify in favor of ssl_verification_mode when mode is client It also added a few SSL configuration validations: - Added a warning log when ssl_* configs are set but ssl_enabled => false - ssl_ceritifcate & ssl_key config validation, including checking if both files are readable. - Ensure no ssl_client_authentication when mode => client - Ensure no ssl_verification_mode when mode => server - Ensure an ssl_certificate is provided when mode => server - Ensure ssl_certificate_authorities is provided when mode => server and it's using the new configuration (ssl_client_authentication)
Fix SSL Subject regression in server mode (#199) * Fix SSL Subject regression in server mode Alters the TCP#decode_buffer signature to accept the _ssl subject_ instead of expecting a ruby socket, so that it can be interoperable between the ruby-based client mode and the netty-powered server mode. In server mode, the SSL subject is extracted _once_ when initializing the connection IFF SSL is enabled and verification is turned on. Co-authored-by: Will Weber <[email protected]> Closes: #159 * include docker jdk17 env Co-authored-by: Will Weber <[email protected]>
PreviousNext