- New configuration option to set TCP keep-alive #16
- Reorder shut down of the two event loops to prevent RejectedExecutionException
- Fix broken 5.0.6 release
- Docs: Set the default_codec doc attribute.
- Restore SSLSUBJECT field when ssl_verify is enabled. #115
- Update Netty/tc-native versions to match those in beats input #113
- Fix bug where codec was not flushed when client disconnected
- Restore INFO logging statement on startup
- Fixed typo in @metadata tag
- Update gemspec summary
- Fix bug where this input would crash logstash during some socket reads when acting as an SSL server
- Fix some documentation issues
- Changed the behaviour of the
host
field to contain the resolved peer hostname for a connection instead of its peer IP - Mark deprecated :data_timeout and :ssl_cacert options as obsolete
and moved the peer's IP to the new field
ip_address
- Fixed regression causing incoming connection host ips being accidentally resolved to hostnames
- Implemented plain socket server in a non-blocking way improving performance and fixing issues for use cases with a large number of concurrent connections
- Version yanked from RubyGems for accidental behaviour change causing unwanted reverse lookups on connections
- Version yanked from RubyGems for packaging issues
- Add documentation for how to use tcp input to accept log4j2 data.
- Add support for proxy protocol
- Relax constraint on logstash-core-plugin-api to >= 1.60 <= 2.99
- Change the log level of the SSLError for the handshake from error to debug logstash-plugins#53
- Republish all the gems under jruby.
- Update the plugin to the version 2.0 of the plugin api, this change is required for Logstash 5.0 compatibility. See elastic/logstash#5141
- Fixed a bug where using a certificate with a passphrase wouldn't work.
- Depend on logstash-core-plugin-api instead of logstash-core, removing the need to mass update plugins on major releases of logstash
- New dependency requirements for logstash-core for the 5.0 release
- Fixed a bug where previous connection would accidentally be closed when accepting new socket connection
- Fixed an issue with log message which used a closed socket's peer address
- properly convert sslsubject to string before assigning to event field, added specs, see logstash-plugins#38
- Deprecate ssl_cacert as it's confusing, does it job but when willing to add a chain of certificated the name and behaviour is a bit confusing.
- Add ssl_extra_chain_certs that allows you to specify a list of certificates path that will be added to the CAStore.
- Make ssl_verify=true as a default value, if using ssl and performing validation is not reasonable as security might be compromised.
- Add tests to verify behaviour under different SSL connection circumstances.
- Fixes #3 and #9.
- Added the receiving port in the event payload, fixes #4
- Fixed malformed SSL crashing Logstash, see logstash-plugins#25
- Dependency on logstash-core update to >= 2.0.0.beta2 < 3.0.0
- removed usage of RSpec.configure, see logstash-plugins#21
- refactored & cleaned up plugin structure, see logstash-plugins#18
- Plugins were updated to follow the new shutdown semantic, this mainly allows Logstash to instruct input plugins to terminate gracefully, instead of using Thread.raise on the plugins' threads. Ref: elastic/logstash#3895
- Dependency on logstash-core update to 2.0