|author||Steve Langasek <email@example.com>||2019-01-22 14:54:11 -0800|
|committer||Steve Langasek <firstname.lastname@example.org>||2019-01-22 14:54:11 -0800|
New upstream version 1.3.0
Diffstat (limited to 'modules/pam_tally/README')
1 files changed, 6 insertions, 6 deletions
diff --git a/modules/pam_tally/README b/modules/pam_tally/README
index 06e8f092..93ceb2ae 100644
@@ -13,11 +13,11 @@ reason pam_tally is deprecated and will be removed in a future release.
pam_tally comes in two parts: pam_tally.so and pam_tally. The former is the PAM
module and the latter, a stand-alone program. pam_tally is an (optional)
application which can be used to interrogate and manipulate the counter file.
-It can display users' counts, set individual counts, or clear all counts.
-Setting artificially high counts may be useful for blocking users without
-changing their passwords. For example, one might find it useful to clear all
-counts every midnight from a cron job. The faillog(8) command can be used
-instead of pam_tally to to maintain the counter file.
+It can display user counts, set individual counts, or clear all counts. Setting
+artificially high counts may be useful for blocking users without changing
+their passwords. For example, one might find it useful to clear all counts
+every midnight from a cron job. The faillog(8) command can be used instead of
+pam_tally to to maintain the counter file.
Normally, failed attempts to access root will not cause the root account to
become blocked, to prevent denial-of-service: if your users aren't given shell
@@ -32,7 +32,7 @@ GLOBAL OPTIONS
- If something weird happens (like unable to open the file), return with
+ If something weird happens (like unable to open the file), return with
PAM_SUCCESS if onerr=succeed is given, else with the corresponding PAM