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.3.0
Date: Mon, 20 Oct 2025 14:58:02 -0400 [thread overview]
Message-ID: <ff56ddac-f08b-4f42-ac25-4a5015d9b1e5@oracle.com> (raw)
This email announces the official release of ktls-utils 1.3.0.
The 1.3.0 release contains an implementation of tlshd support for
certificates using post-quantum encryption algorithms, moves the
configuration file to /etc/tlshd/config in preparation for TLS
session tagging, and adds new GitHub Action workflows.
Work on other new features is ongoing.
Official source code repo:
https://github.com/oracle/ktls-utils/
Release tag:
ktls-utils-1.3.0
Release artifacts:
A source tarball created automatically by GitHub:
https://github.com/oracle/ktls-utils/archive/refs/tags/ktls-utils-1.3.0.tar.gz
A source tarball created with "make dist":
https://github.com/oracle/ktls-utils/releases/download/ktls-utils-1.3.0/ktls-utils-1.3.0.tar.gz
Issues and requests for enhancement:
https://github.com/oracle/ktls-utils/issues
--
Chuck Lever
reply other threads:[~2025-10-20 18:58 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=ff56ddac-f08b-4f42-ac25-4a5015d9b1e5@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;
as well as URLs for NNTP newsgroup(s).