Skip to content

Config file mode - #4367

Open
igaw wants to merge 2 commits into
linux-nvme:masterfrom
igaw:config-file-mode
Open

igaw wants to merge 2 commits into
linux-nvme:masterfrom
igaw:config-file-mode

Conversation

@igaw

@igaw igaw commented Nov 2, 2026

Copy link
Copy Markdown
Collaborator
  • libnvme/config: don't make nvme-fabrics.conf world-readable
  • doc: describe the INI configuration in the fabrics man pages

igaw added 2 commits November 2, 2026 22:29
The emitter wrote every file with mode 0644. nvme-fabrics.conf can hold
KX-HMAC-CHAP secrets and TLS PSKs, so nvme config create and nvme config
convert made them readable by every user. As the file is replaced, a
mode of 0600 set by the admin was reset to 0644 as well.

Create a new file with mode 0600, and keep the mode of an existing one.

Signed-off-by: Daniel Wagner <wagi@monom.org>
The man pages of discover, connect-all and connect still describe the
configuration of nvme-cli 2.x: discovery.conf, and --config naming a
JSON file. Since 3.0, they read nvme-fabrics.conf, and nvme connect
reads a file only with --config. nvme-config-convert(1) says that a
converted file is renamed, but it is kept and a symlink marks it.

Describe what the commands do, and the mode of the file nvme config
create writes.

Signed-off-by: Daniel Wagner <wagi@monom.org>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant