From 0de9dad9ebc88ab044f4b946ef44f63ae2281649 Mon Sep 17 00:00:00 2001 From: Andreas Schneider Date: Thu, 31 Oct 2019 17:10:59 +0100 Subject: [PATCH] docs-xml: Improve krb5_ccache_type documentation Signed-off-by: Andreas Schneider Reviewed-by: Alexander Bokovoy --- docs-xml/manpages/pam_winbind.conf.5.xml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs-xml/manpages/pam_winbind.conf.5.xml b/docs-xml/manpages/pam_winbind.conf.5.xml index 1c48f1bc428..918450c4643 100644 --- a/docs-xml/manpages/pam_winbind.conf.5.xml +++ b/docs-xml/manpages/pam_winbind.conf.5.xml @@ -121,11 +121,15 @@ library). In case of FILE a credential cache in the form of /tmp/krb5cc_UID will be created - in case of DIR you NEED to specify a directory. UID is replaced with the numeric - user id. + user id. The UID directory is being created. The path up to + the directory should already exist. Check the details of the + Kerberos implmentation. When using the KEYRING type, the supported mechanism is KEYRING:persistent:UID, which uses the Linux - kernel keyring to store credentials on a per-UID basis. + kernel keyring to store credentials on a per-UID basis. + The KEYRING has its limitations. As it is secure kernel memory, + for example bulk sorage of credentils is for not possible. When using th KCM type, the supported mechanism is KCM:UID, which uses a Kerberos credential -- 2.34.1