add hash of the kerberos principal to the data being tracked by nfsdcld
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest4 patches 1 replyIn review
- v22 patches 2 repliesSuperseded
- v12 patches 4 repliesSuperseded
Changes in v3 from the cover letter
- we're storing a sha256 hash of a principal instead of the principal itself
Patches in v3 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | nfsdcld: add a "GetVersion" upcallsupport/ utils/ utils/ +1 more | +53 | 0 replies | |
| 2/4 | nfsdcld: add support for upcall version 2support/ utils/ utils/ +2 more | +321 | 0 replies | |
| 3/4 | Add a tool for manipulating the nfsdcld sqlite database schema.configure.ac tools/ tools/ +2 more | +367 | 0 replies | |
| 4/4 | nfsdcld: update nfsdcld.manutils/ | +27 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [nfs-utils PATCH v3 0/4] add hash of the kerberos principal to the data being tracked by nfsdcld
At the spring bakeathon, Chuck suggested that we should store the kerberos principal in addition to the client id string in nfsdcld. The idea is to prevent an illegitimate client from reclaiming another client's opens by supplying that client's id string.
The first patch adds support for a "GetVersion" upcall which allows nfsd to determine the maximum message version that nfsdcld supports. Right now it's based on the value of CLD_UPCALL_VERSION from cld.h, but I was thinking we may wish to add a command-line option (and an nfs.conf) option to make it possible to use a lower version than CLD_UPCALL_VERSION. My thinking here is that an older nfsdcld daemon won't be compatible with the new database schema... rather than worrying about messing with downgrading the database, just use the command-line option to make it behave like an older daemon.
The second patch adds handling for the v2 Cld_Create and Cld_GraceStart upcalls, which can include a hash of the kerberos principal which we'll store along with the client id string in the database. Note that if we're talking to an old kernel that does the v1 upcall, everything still works (we just ignore the new columns in the database).
The third patch adds a tool for manipulating nfsdcld's database schema. It's mostly intended to be used to downgrade the database in the (hopefully rare) event that an admin would want to downgrade nfsdcld. It also provides the ability for fixing broken recovery table names (which nfsdcld also fixes automatically) as well as the ability to print the contents of the database.
The final patch updates the nfsdcld man page.
Changes since v2:
- we're storing a sha256 hash of a principal instead of the principal itself
Changes since v1:
- added a tool for manipulating nfsdcld's sqlite database schema
- updated the nfsdcld man page
Scott Mayhew (4):
nfsdcld: add a "GetVersion" upcall
nfsdcld: add support for upcall version 2
Add a tool for manipulating the nfsdcld sqlite database schema.
nfsdcld: update nfsdcld.man
configure.ac | 1 + support/include/cld.h | 41 ++++- tools/Makefile.am | 4 + tools/clddb-tool/Makefile.am | 13 ++ tools/clddb-tool/clddb-tool.man | 83 ++++++++++ tools/clddb-tool/clddb-tool.py | 266 ++++++++++++++++++++++++++++++++ utils/nfsdcld/cld-internal.h | 13 +- utils/nfsdcld/nfsdcld.c | 140 ++++++++++++++--- utils/nfsdcld/nfsdcld.man | 32 +++- utils/nfsdcld/sqlite.c | 239 +++++++++++++++++++++++----- utils/nfsdcld/sqlite.h | 2 + 11 files changed, 765 insertions(+), 69 deletions(-) create mode 100644 tools/clddb-tool/Makefile.am create mode 100644 tools/clddb-tool/clddb-tool.man create mode 100644 tools/clddb-tool/clddb-tool.py
Signature · 1 line
2.17.2