From: Benjamin Coddington <bcodding@hammerspace.com>
To: Steve Dickson <steved@redhat.com>,
Benjamin Coddington <bcodding@hammerspace.com>
Cc: linux-nfs@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>,
NeilBrown <neil@brown.name>, Jeff Layton <jlayton@kernel.org>
Subject: [PATCH v1 0/2] nfs-utils: signed filehandle support
Date: Fri, 16 Jan 2026 13:18:01 -0500 [thread overview]
Message-ID: <cover.1768586942.git.bcodding@hammerspace.com> (raw)
Here are two patches allowing userspace to set a secret key for kNFSD to
sign filehandles, and also set the option to sign filehandles for an
export.
The secret key passed to the server is the first 128 bits of a sha1 hash of
the contents of a file configured via the nfs.conf server section
"fh_key_file". Exports that have the option "sign_fh" set will cause the
server to use this key to append an 8-byte siphash of the filehandle onto
each filehandle.
This version of the userspace patches correspond with the v1 of the kernel
changes which have been posted here:
https://lore.kernel.org/linux-nfs/C69B1F13-7248-4CAF-977C-5F0236B0923A@hammerspace.com/T/#t
This work is based on a branch that includes Jeff Layton's patch for
min-threads:
https://lore.kernel.org/linux-nfs/20260112-minthreads-v1-1-30c5f4113720@kernel.org/
Comments and critique welcomed.
Benjamin Coddington (2):
nfsdctl/rpc.nfsd: Add support for passing encrypted filehandle key
exportfs: Add support for export option sign_fh
configure.ac | 4 +-
nfs.conf | 1 +
support/include/nfs/export.h | 2 +-
support/include/nfslib.h | 2 +
support/nfs/Makefile.am | 4 +-
support/nfs/exports.c | 4 ++
systemd/nfs.conf.man | 1 +
utils/exportfs/exportfs.c | 2 +
utils/exportfs/exports.man | 9 ++++
utils/nfsd/nfsd.c | 16 ++++++-
utils/nfsd/nfssvc.c | 26 +++++++++++
utils/nfsd/nfssvc.h | 1 +
utils/nfsdctl/nfsd_netlink.h | 2 +
utils/nfsdctl/nfsdctl.c | 86 +++++++++++++++++++++++++++++++++++-
14 files changed, 153 insertions(+), 7 deletions(-)
base-commit: 612e407c46b848932c32be00b835a7b5317e3d08
prerequisite-patch-id: cc4d768b1f6935b3c94ae87bd0389270717bc5b0
prerequisite-patch-id: c1ef8324c84a18d3ba29a971cb43b16798d71166
--
2.50.1
next reply other threads:[~2026-01-16 18:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 18:18 Benjamin Coddington [this message]
2026-01-16 18:18 ` [PATCH v1 1/2] nfsdctl/rpc.nfsd: Add support for passing encrypted filehandle key Benjamin Coddington
2026-01-16 18:18 ` [PATCH v1 2/2] exportfs: Add support for export option sign_fh Benjamin Coddington
2026-01-17 21:53 ` [PATCH v1 1/2] nfsdctl/rpc.nfsd: Add support for passing encrypted filehandle key NeilBrown
2026-01-18 16:59 ` Benjamin Coddington
2026-01-18 20:09 ` Steve Dickson
2026-01-18 20:38 ` Benjamin Coddington
2026-01-18 23:05 ` NeilBrown
2026-01-21 15:24 ` Steve Dickson
2026-01-21 22:37 ` NeilBrown
2026-01-21 17:06 ` Benjamin Coddington
2026-01-21 22:38 ` NeilBrown
2026-01-21 22:59 ` Benjamin Coddington
2026-01-17 21:59 ` [PATCH v1 2/2] exportfs: Add support for export option sign_fh NeilBrown
2026-01-18 17:00 ` 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.1768586942.git.bcodding@hammerspace.com \
--to=bcodding@hammerspace.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox