sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-08-04 08:22:08 +03:00
Code Activity

docs-xml: pam_winbind manpage: grammar and typos

Browse Source 
Signed-off-by: Rowland Penny <rpenny@samba.org>
Reviewed-by: Jeremy Allison <jra@samba.org>

Autobuild-User(master): Jeremy Allison <jra@samba.org>
Autobuild-Date(master): Wed Aug 26 04:44:51 UTC 2020 on sn-devel-184
This commit is contained in:
Rowland Penny
2020-08-25 13:19:28 +01:00
committed by Jeremy Allison
parent 830c020645
commit e9137a9e9d
1 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs-xml/manpages/pam_winbind.8.xml
View File

@ -165,23 +165,23 @@
(when the DIR type is supported by the system's Kerberos (when the DIR type is supported by the system's Kerberos
library). In case of FILE a credential cache in the form of library). In case of FILE a credential cache in the form of
/tmp/krb5cc_UID will be created - in case of DIR you NEED /tmp/krb5cc_UID will be created - in case of DIR you NEED
to specify a directory. UID is replaced with the numeric to specify a directory which must exist, the UID directory
user id. The UID directory is being created. The path up to will be created in the specified directory.
the directory should already exist. Check the details of the In all cases UID is replaced with the numeric user id.
Kerberos implmentation.</para> Check the details of the Kerberos implementation.</para>
<para>When using the KEYRING type, the supported mechanism is <para>When using the KEYRING type, the supported mechanism is
<quote>KEYRING:persistent:UID</quote>, which uses the Linux <quote>KEYRING:persistent:UID</quote>, 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, KEYRING has limitations. For example, it is secure kernel memory,
for example bulk sorage of credentils is for not possible.</para> so bulk storage of credentials is not possible.</para>
<para>When using th KCM type, the supported mechanism is <para>When using the KCM type, the supported mechanism is
<quote>KCM:UID</quote>, which uses a Kerberos credential <quote>KCM:UID</quote>, 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 KEYRING. This is the recommended choice on latest Linux
distributions, offering a Kerberos Credential Manager. If not distributions that offer a Kerberos Credential Manager. If not,
we suggest to use KEYRING as those are the most secure and we suggest to use KEYRING, as those are the most secure and
predictable method.</para> predictable method.</para>
<para>It is also possible to define custom filepaths and use the "%u" <para>It is also possible to define custom filepaths and use the "%u"