You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Tibor Benke (JIRA)" <ji...@apache.org> on 2013/09/06 13:37:56 UTC
[jira] [Updated] (LOG4J2-338) Add TLS support to SyslogAppender
[ https://issues.apache.org/jira/browse/LOG4J2-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tibor Benke updated LOG4J2-338:
-------------------------------
Attachment: documentation_notes.patch
> 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
> Fix For: 2.0-beta9
>
> Attachments: add_TLSSyslogAppender.zip, documentation_notes.patch
>
>
> 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-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org