keyrings.7: document description restriction for logon keys
PATCH 3/4 keyrings.7: document description restriction for logon keys
"logon" type has additional check that enforces colon-separated prefix in key descriptions.
* man7/keyrings.7 (.SS Key types) <.TP .IR """logon""">: Document restriction imposed on logon key descriptions.
--- man7/keyrings.7 | 5 +++++ 1 file changed, 5 insertions(+)
man7/keyrings.7 +5 -0
@@ -142,6 +142,11 @@ operation), meaning that the key payload is never visible from user space. This is suitable for storing username-password pairs that should not be readable from user space. +.IP +Key description of a logon key must start with non-empty colon-delimited +prefix with the purpose to identify the service to which it belongs. +(contrary to keys of the "user" type, where this practice is recommended +but is not enforced). .TP .IR """big_key""" " (since Linux 3.13)" .\" commit ab3c3587f8cda9083209a61dbe3a4407d3cada10
Signature · 6 lines
2.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): 20170911031112.GA5300-ZbobWygYI+YXGNroddHbYwC/[email protected]
Hi Eugene
Quoted 2 lines · Eugene Syromyatnikov
"logon" type has additional check that enforces colon-separated prefix in key descriptions.
Thanks. Patch applied, with some tweaks.
Cheers,
Michael
Quoted 15 lines
* man7/keyrings.7 (.SS Key types) <.TP .IR """logon""">: Document restriction imposed on logon key descriptions.
Signed-off-by Eugene Syromyatnikov <[email protected]>--- man7/keyrings.7 | 5 +++++ 1 file changed, 5 insertions(+)man7/keyrings.7 +0
-0@@ -142,6 +142,11 @@ operation), meaning that the key payload is never visible from user space.
man7/keyrings.7 operation), · line 152
Quoted 10 lines
man7/keyrings.7 +5
-0This is suitable for storing username-password pairs that should not be readable from user space. +.IP +Key description of a logon key must start with non-empty colon-delimited +prefix with the purpose to identify the service to which it belongs. +(contrary to keys of the "user" type, where this practice is recommended +but is not enforced). .TP .IR """big_key""" " (since Linux 3.13)" .\" commit ab3c3587f8cda9083209a61dbe3a4407d3cada10
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html