[NIFI-8462] Refactor PutSyslog and ListenSyslog using Netty

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Resolved
• Affects Version/s: 1.13.2
• Fix Version/s: 1.14.0
• Component/s: Extensions
• Labels: Netty SSLEngine security
• Assignee: David Handermann
• Reporter: David Handermann
• Created: 22/Apr/21 14:57
• Updated: 22/Oct/21 18:52
• Resolved: 25/May/21 14:56

Description

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.

Issue Links

• causes: NIFI-9223 ListenSyslog cannot listen on 0.0.0.0
• fixes: NIFI-6414 java.net.PortUnreachableException: null when using DatagramChannelSender (UDP)
• is related to: NIFI-7468 Improve internal handling of SSL channels
• relates to: NIFI-8672 Intermittent Test Failures in TestListenSyslog
• relates to: NIFI-8616 Migrate SSL socket code to use Netty
• relates to: NIFI-8792 Refactor ListenRELP using Netty
• relates to: NIFI-9326 Add Socket Keep Alive Property to ListenSyslog
• links to: GitHub Pull Request #5044