New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide SSL/TLS support #27

Open
sherry-ger opened this Issue May 18, 2016 · 4 comments

Comments

Projects
None yet
3 participants
@sherry-ger
Copy link

sherry-ger commented May 18, 2016

  • Version: 2.3
  • Operating System: CentOS 6.5

TCP input can be used as a workaround but it would be nice to have SSL/TLS support for syslog input.

@jordansissel

This comment has been minimized.

Copy link
Contributor

jordansissel commented May 18, 2016

I think my preference for solving this is to move syslog support into a codec (or a filter) and move everyone to use the tcp and udp inputs for the network part of syslog.

@jordansissel

This comment has been minimized.

Copy link
Contributor

jordansissel commented May 18, 2016

(the impact would be that users wanting tls/ssl could use that feature from the tcp input once we did the syslog codec or filter)

@alesnav

This comment has been minimized.

Copy link

alesnav commented Dec 15, 2016

Hello there!

Do you have any ETA for this enhancement?

It would be nice to have this functionality available to secure the whole log path (source -> logstash -> elasticsearch).

Thanks,
Best regards

@jordansissel

This comment has been minimized.

Copy link
Contributor

jordansissel commented Dec 15, 2016

@alesnav I recommend using the TCP input which has TLS support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment