[
https://issues.apache.org/jira/browse/LOG4J2-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757233#comment-13757233
]
Ralph Goers commented on LOG4J2-338:
------------------------------------
I was able to apply the patch after some editing. All the files were missing
license headers and I have to fix some checkstyle issues and create some
documentation.
> Add TLS support to SyslogAppender
> ---------------------------------
>
> Key: LOG4J2-338
> URL: https://issues.apache.org/jira/browse/LOG4J2-338
> Project: Log4j 2
> Issue Type: New Feature
> Components: Appenders, Core
> Reporter: Tibor Benke
> Attachments: add_TLSSyslogAppender.zip
>
>
> Currently, there is no TLS support in SyslogAppender.
> It would be very nice if one could send encrypted syslog messages to syslog
> daemons.
> I think the use cases are obvious: you want to protect your syslog messages
> against masquerade, modification and disclosure.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
