Clarify documentation of password quality check modules

Be clearer in the info documentation that the part of the policy
name before the colon is the name of the module, not the static
string "module".  State explicitly that "builtin" can be used as the
module name to identify built-in policies.

Use the same terminology in kadm5_pwcheck(3) as the info documentation,
changing test-name to policy-name and vendor to module-name.  State
explicitly how the module name and policy name are used to select which
policies to run.

Rephrase a few sentences, add a paragraph break, and fix a few typos
for clarity.

Signed-off-by: Love Hornquist Astrand <lha@h5l.org>
This commit is contained in:
Russ Allbery
2010-01-14 17:40:16 -08:00
committed by Love Hornquist Astrand
parent 80317bbd20
commit 3441bbb98e
2 changed files with 27 additions and 12 deletions

View File

@@ -422,16 +422,18 @@ controls, add lines similar to the following to your
@example
[password_quality]
policies = external-check builtin:minimum-length module:policyname
policies = external-check builtin:minimum-length modulename:policyname
external_program = /bin/false
policy_libraries = @var{library1.so} @var{library2.so}
@end example
In @samp{[password_quality]policies} the module name is optional if
the policy name is unique in all modules (members of
@samp{policy_libraries}).
@samp{policy_libraries}). All built-in policies can be qualified with
a module name of @samp{builtin} to unambiguously specify the built-in
policy and not a policy by the same name from a loaded module.
The built-in polices are
The built-in policies are
@itemize @bullet