[
https://issues.apache.org/jira/browse/NIFI-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15038016#comment-15038016
]
Oleg Zhurakousky commented on NIFI-1227:
----------------------------------------
In fact there are a lot of inner classes in ListenerSyslog that are only
referenced internally.
Some of them new (as mentioned above), some existed before. Below is the list
(*bold* demarcates the new)
IMHO the new once should definitely become private. The existing once while
technically would be a breaking change I still think they fall into the pre-1.0
compromise and should be made private before it's too late and someone starts
depending on it, but would be interested in [[email protected]] opinion on that
as it seems to be one of those grey areas.
_DatagramChannelReader_
_SocketChannelDispatcher_
_SocketChannelHandler_
*_SSLSocketChannelHandler_*
_RawSyslogEvent_
*_SocketChannelAttachment_*
> ListenSyslog should support TLS
> -------------------------------
>
> Key: NIFI-1227
> URL: https://issues.apache.org/jira/browse/NIFI-1227
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 0.4.0
> Reporter: Andre
> Assignee: Bryan Bende
> Fix For: 0.4.0
>
> Attachments: NIFI-1227.patch
>
>
> It would be good if the ListenSyslog supported TLS as described here:
> http://www.rsyslog.com/doc/v8-stable/tutorials/tls_cert_summary.html
> and
> https://www.balabit.com/sites/default/files/documents/syslog-ng-ose-latest-guides/en/syslog-ng-ose-guide-admin/html/procedure-configuring-tls-server.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
