You are viewing a plain text version of this content. The canonical link for it is here.

Posted to builds@fluss.apache.org by GitBox <gi...@apache.org> on 2026/10/14 15:46:43 UTC

[GH] (fluss/netty-tls-pipeline): Workflow run "CI" is working again!

The GitHub Actions job "CI" on fluss.git/netty-tls-pipeline has succeeded.
Run started by GitHub user morazow (triggered by morazow).

Head commit for run:
4f7307c6458b1fe69b39bd1454f5214900c46e0d / morazow <m....@gmail.com>
[FIP-29][rpc] Wire TLS encryption into the server Netty pipeline

Listeners named in security.ssl.enabled.listeners now encrypt their
connections: the server channel initializer adds an SslHandler first in
the pipeline, so framing and authentication run inside TLS. The server
SSL context is built once in FlussProtocolPlugin#setup, so invalid TLS
settings fail the server at startup, and a name in
security.ssl.enabled.listeners that matches no listener is rejected
rather than leaving the intended listener on plaintext.

SslHandler accepts only ByteBufs, while the log fetch path writes
file-backed records as a zero-copy FileRegion. TlsFileRegionHandler
copies those regions into memory before encryption, so TLS listeners
give up zero-copy log fetches.

Report URL: https://github.com/apache/fluss/actions/runs/38572718086

With regards,
GitHub Actions via GitBox