Panic when using TLS configuration (Go 1.7.4)#15
Panic when using TLS configuration (Go 1.7.4)#15christiangalsterer merged 3 commits intochristiangalsterer:masterfrom
Conversation
|
Thanks for the contribution. Will look into it the next days/weekend. |
|
Can we get a new release/build please? |
|
I will look into another item #14 on the weekend and depending on the outcome I will cut a release on the weekend. |
|
@MarkSonghurst Can you share the ssl config that worked for you with your updates? |
|
|
For logstash |
|
Without my PR I would get an immediate Go panic when the SSL config was loaded, and httpbeat would terminate. I'm really surprised the guys in #14 are not seeing that also. Anyway, once I fixed the panic, I had some error messages on STDOUT about an invalid cert which led me to use both the Incidently, the comment in the logstash section: |
|
Thanks - I can set those properties yet they don't work for me. My suspicion is that the "verification_mode" property doesn't work properly as I can curl the endpoint with the --insecure option which is supposed to be the equivalent of "verification_mode: none" but httpbeat seems to still try to verify the hostname against the common name in the certificate. Unfortunately the system I am trying to call is creating a self signed certificate that does not have the proper host name... |
|
Release 3.2.0 now available |
I would get a panic if I attempted to use any TLS related configuration when building httpbeats on Go 1.7.4
I'm slightly unsure how the function poller.go convertTLSConfig() could have ever worked, maybe something got tightened up in Go 1.7.4