From: Xin Long <lucien.xin@gmail.com>
To: kernel-tls-handshake@lists.linux.dev
Cc: Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH 0/2] tlshd: do not set conn errcode to GnuTLS errors in QUIC handshake
Date: Thu, 25 Sep 2025 12:38:04 -0400 [thread overview]
Message-ID: <cover.1758818286.git.lucien.xin@gmail.com> (raw)
This series aligns QUIC error handling in tlshd with the TLS 1.3 code.
- On GnuTLS failure during session setup, log the error and leave
parms session_status = EIO.
- On GnuTLS failure during handshake, log the error and set conn
errcode = EACCES.
Xin Long (2):
tlshd: leave session_status as EIO on GnuTLS failure in QUIC session
setup
tlshd: set conn errcode to EACCES on GnuTLS failure in QUIC handshake
src/tlshd/client.c | 42 ++++++++++++++---------------
src/tlshd/quic.c | 66 ++++++++++++++++++++++++++--------------------
src/tlshd/server.c | 29 +++++++++-----------
3 files changed, 70 insertions(+), 67 deletions(-)
--
2.47.1
next reply other threads:[~2025-09-25 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 16:38 Xin Long [this message]
2025-09-25 16:38 ` [PATCH 1/2] tlshd: leave session_status as EIO on GnuTLS failure in QUIC session setup Xin Long
2025-09-25 16:38 ` [PATCH 2/2] tlshd: set conn errcode to EACCES on GnuTLS failure in QUIC handshake Xin Long
2025-09-26 13:14 ` [PATCH 0/2] tlshd: do not set conn errcode to GnuTLS errors " Chuck Lever
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=cover.1758818286.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail.com \
--cc=chuck.lever@oracle.com \
--cc=kernel-tls-handshake@lists.linux.dev \
/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