From: Chuck Lever <chuck.lever@oracle.com>
To: kernel-tls-handshake <kernel-tls-handshake@lists.linux.dev>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
linux-nvme@lists.infradead.org
Subject: [ANNOUNCE] ktls 1.4.0
Date: Sat, 9 May 2026 13:04:41 -0400 [thread overview]
Message-ID: <f44ebcff-446a-4582-82af-5f206bb0823a@oracle.com> (raw)
This email announces the official release of ktls-utils 1.4.0.
The 1.4.0 release contains an implementation of tlshd support for TLS
record size limits, QUIC session tickets, and TLS session tags. It also
adds kernel capability detection and the ability to reload the tlshd
config file without restarting the daemon.
Work on other new features is ongoing.
Official source code repo:
https://github.com/oracle/ktls-utils/
Release tag:
ktls-utils-1.4.0
Release artifacts:
A source tarball created automatically by GitHub:
https://github.com/oracle/ktls-utils/archive/refs/tags/ktls-utils-1.4.0.tar.gz
A source tarball created with "make dist":
https://github.com/oracle/ktls-utils/releases/download/ktls-utils-1.4.0/ktls-utils-1.4.0.tar.gz
Issues and requests for enhancement:
https://github.com/oracle/ktls-utils/issues
--
Chuck Lever
reply other threads:[~2026-05-09 17:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f44ebcff-446a-4582-82af-5f206bb0823a@oracle.com \
--to=chuck.lever@oracle.com \
--cc=kernel-tls-handshake@lists.linux.dev \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox