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.