From: Rowland Penny Date: Tue, 25 Aug 2020 12:19:28 +0000 (+0100) Subject: docs-xml: pam_winbind manpage: grammar and typos X-Git-Tag: samba-4.14.0rc1~1399 X-Git-Url: http://git.samba.org/?a=commitdiff_plain;ds=sidebyside;h=e9137a9e9dd600ef1f34f82cf8301883ea9c045c;p=samba.git docs-xml: pam_winbind manpage: grammar and typos Signed-off-by: Rowland Penny Reviewed-by: Jeremy Allison Autobuild-User(master): Jeremy Allison Autobuild-Date(master): Wed Aug 26 04:44:51 UTC 2020 on sn-devel-184 --- diff --git a/docs-xml/manpages/pam_winbind.8.xml b/docs-xml/manpages/pam_winbind.8.xml index 32030ef0ecc..171bb408757 100644 --- a/docs-xml/manpages/pam_winbind.8.xml +++ b/docs-xml/manpages/pam_winbind.8.xml @@ -165,23 +165,23 @@ (when the DIR type is supported by the system's Kerberos 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. The UID directory is being created. The path up to - the directory should already exist. Check the details of the - Kerberos implmentation. + to specify a directory which must exist, the UID directory + will be created in the specified directory. + In all cases UID is replaced with the numeric user id. + Check the details of the Kerberos implementation. 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. - The KEYRING has its limitations. As it is secure kernel memory, - for example bulk sorage of credentils is for not possible. + KEYRING has limitations. For example, it is secure kernel memory, + so bulk storage of credentials is not possible. - When using th KCM type, the supported mechanism is + When using the KCM type, the supported mechanism is KCM:UID, which uses a Kerberos credential - manaager to store credentials on a per-UID basis similar to + manager to store credentials on a per-UID basis similar to KEYRING. This is the recommended choice on latest Linux - distributions, offering a Kerberos Credential Manager. If not - we suggest to use KEYRING as those are the most secure and + distributions that offer a Kerberos Credential Manager. If not, + we suggest to use KEYRING, as those are the most secure and predictable method. It is also possible to define custom filepaths and use the "%u"