zfs/man/man7
Kyle Evans 5c46baa1ce
zfsprops(7): attempt to clarify the keylocation description
The current description is somewhat difficult to parse through, and in
some cases is a little unclear as to the behavior.

Split it into a paragraphs based on the three distinct behaviors you
may get: prompt, file URL, HTTP(S) URL.  The descriptions of the file
and HTTP(s) behavior seems fine, but prompt is a little vague- expand
on it and make it clear that the behavior is actively based on whether
the inquisitor of key-data is provided with a tty for stdin or not.

Also clarify *why* one shouldn't "place keys which should be kept secret
on the command line" and note that you *have* to supply the key via
stdin if it's a raw key, just to be sure.

Reviewed-by: Allan Jude <allan@klarasystems.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Alexander Motin <alexander.motin@TrueNAS.com>
Reviewed-by: George Melikov <mail@gmelikov.ru>
Signed-off-by: Kyle Evans <kevans@FreeBSD.org>
Closes #17742
2025-09-15 10:26:17 -07:00
..
dracut.zfs.7 manuals: Audit/bump dates for last content change 2025-08-28 16:26:16 -07:00
vdevprops.7 Detect a slow raidz child during reads 2025-09-10 15:25:03 -07:00
zfsconcepts.7 manuals: Audit/bump dates for last content change 2025-08-28 16:26:16 -07:00
zfsprops.7 zfsprops(7): attempt to clarify the keylocation description 2025-09-15 10:26:17 -07:00
zpool-features.7 manuals: Audit/bump dates for last content change 2025-08-28 16:26:16 -07:00
zpoolconcepts.7 manuals: Audit/bump dates for last content change 2025-08-28 16:26:16 -07:00
zpoolprops.7 manuals: Audit/bump dates for last content change 2025-08-28 16:26:16 -07:00