ssl_enable: true used alone raise an exception

[collimarco]

The readme describes the following configuration:

LogStashLogger.new(type: :tcp, host: 'listener.logz.io', port: 5000, ssl_enable: true)

However that raise an exception:

ERROR -- : [LogStashLogger::Device::TCP] TypeError - wrong argument (NilClass)! (Expected kind of OpenSSL::SSL::SSLContext)

When ssl_context is not passed explicitly, you probably need to create an ssl_context automatically with VERIFY_PEER.

[collimarco]

The problem is also relevant for the Rails integration when you use:

config.logstash.ssl_enable = true

[dwbutler]

After some investigation, I have discovered that this is a new problem starting with Ruby 2.4. The behavior of OpenSSL::SSL::SSLSocket::new has changed. In Ruby <= 2.3, the method signature is new(io, ctx = nil). In Ruby 2.4+, you must pass either one argument or both. You can't pass a nil context.

[dwbutler]

Fix released in 0.26.1.