From: Benjamin Coddington <ben.coddington@hammerspace.com>
To: Steve Dickson <steved@redhat.com>
Cc: linux-nfs@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>
Subject: [PATCH 0/1] nfs-utils: nfs-fh-verify signed filehandles
Date: Tue, 26 May 2026 10:40:48 -0400 [thread overview]
Message-ID: <cover.1779805943.git.bcodding@hammerspace.com> (raw)
We've had a lot of folks configure signed filehandles, and then wonder "Is
this thing actually working?". Given the various filehandle lengths and
types, it can be pretty difficult to know if the kernel is actually
correctly signing its filehandles. Claude and I wrote this tool that allows
anyone to verify the correct functioning of filehandle signing given the
original key and a list of filehandles.
Beyond that, this tool shows a way to monitor the configured state of signed
filehandles in a distributed installation.
Benjamin Coddington (1):
nfs-fh-verify: add tool to validate kNFSD filehandle signatures
configure.ac | 7 +
tools/Makefile.am | 4 +
tools/nfs-fh-verify/Makefile.am | 10 +
tools/nfs-fh-verify/main.c | 337 ++++++++++++++++++++++++++
tools/nfs-fh-verify/nfs-fh-verify.man | 171 +++++++++++++
5 files changed, 529 insertions(+)
create mode 100644 tools/nfs-fh-verify/Makefile.am
create mode 100644 tools/nfs-fh-verify/main.c
create mode 100644 tools/nfs-fh-verify/nfs-fh-verify.man
base-commit: a806c9d65662ecf5d40c00d60a514e13ada8d76e
--
2.53.0
next reply other threads:[~2026-05-26 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 14:40 Benjamin Coddington [this message]
2026-05-26 14:40 ` [PATCH 1/1] nfs-fh-verify: add tool to validate kNFSD filehandle signatures Benjamin Coddington
2026-05-26 15:37 ` [PATCH 0/1] nfs-utils: nfs-fh-verify signed filehandles Chuck Lever
2026-05-26 16:13 ` Benjamin Coddington
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.1779805943.git.bcodding@hammerspace.com \
--to=ben.coddington@hammerspace.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.