[ 
https://issues.apache.org/jira/browse/NIFI-8462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351115#comment-17351115
 ] 

ASF subversion and git services commented on NIFI-8462:
-------------------------------------------------------

Commit a3365c883359d8a06c0ef4e9b370aa83e7d6c67b in nifi's branch 
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a3365c8 ]

NIFI-8462 Refactored PutSyslog and ListenSyslog using Netty

- Added nifi-event-transport module encapsulating Netty classes
- Refactored unit tests for PutSyslog and ListenSyslog
- Removed integration tests for PutSyslog and ListenSyslog

NIFI-8462 Added context.yield() in PutSyslog when no FlowFiles and addressed 
other issues

NIFI-8462 Removed unused import of ExpressionLanguageScope

Signed-off-by: Nathan Gough <thena...@gmail.com>

This closes #5044.


> Refactor PutSyslog and ListenSyslog using Netty
> -----------------------------------------------
>
>                 Key: NIFI-8462
>                 URL: https://issues.apache.org/jira/browse/NIFI-8462
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.13.2
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Major
>              Labels: Netty, SSLEngine, security
>             Fix For: 1.14.0
>
>          Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> Multiple extension and framework components leverage custom socket handling 
> classes for sending and receiving messages.  These custom classes include 
> {{SSLSocketChannel}}, which handles handshaking and interaction with 
> {{SSLEngine}}.  Custom {{SSLEngine}} handling is prone to errors, and the 
> current implementation has issues with TLS 1.3.  Rather than continuing to 
> maintain custom {{SSLEngine}} handling, moving to a solution based on Netty 
> provides a cleaner approach.
> The purpose of this issue is to refactor {{PutSyslog}} and {{ListenSyslog}} 
> using Netty to provide a way forward for other impacted components.  The 
> changes should maintain compatibility with existing TCP and UDP protocol 
> configurations.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to