linux登录次数限制
2012-06-21 16:41
253 查看
参阅:http://fedoranews.org/contributors/sonny_nguyen/pam/
http://yodeforever.blog.163.com/blog/static/66402950201151365136/
] [ magic_root ] [ even_deny_root_account ] [ deny=
[ per_user ] [ no_lock_time ] [ no_reset ] [ audit ] [ silent ] [ no_log_info ]
] [ --quiet ]
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.
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 accounts and root may
only login via su or at the machine console (not telnet/rsh, etc), this is safe.
This can be used for auth and account module types.
If something weird happens (like unable to open the file), return with PAM_SUCCESS if
Will log the user name into the system log if the user is not found.
Don't print informative messages.
Don't log informative messages via syslog(3).
AUTH OPTIONS
Authentication phase first checks if user should be denied access and if not it increments attempted login counter. Then on call to pam_setcred(3) it resets the attempts counter.
Otherwise the account is locked until the lock is removed by a manual intervention of the system administrator.
If the module is invoked by a user with uid=0 the counter is not incremented. The sysadmin should use this for user launched services, like su, otherwise this argument should be omitted.
Do not use the .fail_locktime field in
Don't reset count on successful entry, only decrement.
Root account can become unavailable.
If
Don't use .fail_locktime filed in
ACCOUNT OPTIONS
Account phase resets attempts counter if the user is not magic root. This phase can be used optionally for services which don't call pam_setcred(3) correctly
or if the reset should be done regardless of the failure of the account phase of other modules.
If the module is invoked by a user with uid=0 the counter is not incremented. The sysadmin should use this for user launched services, like su, otherwise this argument should be omitted.
Don't reset count on successful entry, only decrement.
A invalid option was given, the module was not able to retrieve the user name, no valid counter file was found, or too many failed logins.
PAM_SUCCESS
Everything was successful.
PAM_USER_UNKNOWN
User not known.
http://yodeforever.blog.163.com/blog/static/66402950201151365136/
pam_tally - login counter (tallying) module
pam_tally.so[ file=
/path/to/counter] [ onerr=[
fail|
succeed]
] [ magic_root ] [ even_deny_root_account ] [ deny=
n] [ lock_time=
n] [ unlock_time=
n]
[ per_user ] [ no_lock_time ] [ no_reset ] [ audit ] [ silent ] [ no_log_info ]
pam_tally[ --file
/path/to/counter] [ --user
username] [ --reset[=
n]
] [ --quiet ]
6.32.1.�DESCRIPTION
This module maintains a count of attempted accesses, can reset count on success, can deny access if too many attempts fail.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.
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 accounts and root may
only login via su or at the machine console (not telnet/rsh, etc), this is safe.
6.32.2.�OPTIONS
GLOBAL OPTIONSThis can be used for auth and account module types.
onerr=[][/code]fail|[code]succeed
If something weird happens (like unable to open the file), return with PAM_SUCCESS if
onerr=.succeedis given, else with the
corresponding PAM error code.
[code]file=/path/to/counter
File where to keep counts. Default is [code]/var/log/faillog
audit
Will log the user name into the system log if the user is not found.
silent
Don't print informative messages.
no_log_info
Don't log informative messages via syslog(3).
AUTH OPTIONS
Authentication phase first checks if user should be denied access and if not it increments attempted login counter. Then on call to pam_setcred(3) it resets the attempts counter.
deny=.n
Deny access if tally for this user exceeds [code]n
lock_time=seconds after failed attempt.n
Always deny for [code]n
unlock_time=seconds after failed attempt. If this option is used the user will be locked out for the specified amount of time after he exceeded his maximum allowed attempts.n
Allow access after [code]n
Otherwise the account is locked until the lock is removed by a manual intervention of the system administrator.
magic_root
If the module is invoked by a user with uid=0 the counter is not incremented. The sysadmin should use this for user launched services, like su, otherwise this argument should be omitted.
no_lock_time
Do not use the .fail_locktime field in
/var/log/faillogfor this user.
no_reset
Don't reset count on successful entry, only decrement.
even_deny_root_account
Root account can become unavailable.
per_user
If
/var/log/faillogcontains a non-zero .fail_max/.fail_locktime field for this user then use it instead of
deny=n/ [code]lock_time=nparameter.
[code]no_lock_time
Don't use .fail_locktime filed in
/var/log/faillogfor this user.
ACCOUNT OPTIONS
Account phase resets attempts counter if the user is not magic root. This phase can be used optionally for services which don't call pam_setcred(3) correctly
or if the reset should be done regardless of the failure of the account phase of other modules.
magic_root
If the module is invoked by a user with uid=0 the counter is not incremented. The sysadmin should use this for user launched services, like su, otherwise this argument should be omitted.
no_reset
Don't reset count on successful entry, only decrement.
6.32.3.�MODULE TYPES PROVIDED
Theauthand
accountmodule types are provided.
6.32.4.�RETURN VALUES
PAM_AUTH_ERRA invalid option was given, the module was not able to retrieve the user name, no valid counter file was found, or too many failed logins.
PAM_SUCCESS
Everything was successful.
PAM_USER_UNKNOWN
User not known.
6.32.5.�EXAMPLES
Add the following line to/etc/pam.d/loginto lock the account after too many failed logins. The number of allowed fails is specified by
/var/log/faillogand needs to be set with pam_tally or faillog(8) before.
auth required pam_securetty.so auth required pam_tally.so per_user auth required pam_env.so auth required pam_unix.so auth required pam_nologin.so account required pam_unix.so password required pam_unix.so session required pam_limits.so session required pam_unix.so session required pam_lastlog.so nowtmp session optional pam_mail.so standard
6.32.6.�AUTHOR
pam_tally was written by Tim Baverstock and Tomas Mraz.相关文章推荐
- Linux如何通过PAM限制用户登录失败次数
- Linux如何通过PAM限制用户登录失败次数
- Linux下设置限制登录oracle数据库及Linux操作系统的IP、尝试登录次数及长时间空闲后断开
- 利用pam限制linux登录次数
- Linux 限制root用户远程登录-ssh
- Linux的su命令,sudo命令和限制root远程登录
- asp.net限制用户登录错误次数
- mysql会话控制限制登录次数(connection_control插件)
- 限制登录次数
- 拦截器限制用户访问次数和验证用户登录代码
- centos 下 限制同一用户在同一时间的登录次数
- 取消Oracle用户密码登录错误次数限制
- 配置 limits.conf 限制 Linux 用户登录数量
- linux系统如何限制其他用户登录
- Linux笔记(su切换用户,sudo命令*,限制root远程登录)
- [转]CentO下限制SSH登录次数
- Shiro security限制登录尝试次数