{"id":4740,"date":"2022-12-20T18:36:50","date_gmt":"2022-12-20T21:36:50","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/faillock-conf-man5\/"},"modified":"2022-12-20T18:36:50","modified_gmt":"2022-12-20T21:36:50","slug":"faillock-conf-man5","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/faillock-conf-man5\/","title":{"rendered":"FAILLOCK.CONF (man5)"},"content":{"rendered":"<h1 align=\"center\">FAILLOCK.CONF<\/h1>\n<p> <a href=\"#NAME\">NAME<\/a><br \/> <a href=\"#DESCRIPTION\">DESCRIPTION<\/a><br \/> <a href=\"#OPTIONS\">OPTIONS<\/a><br \/> <a href=\"#EXAMPLES\">EXAMPLES<\/a><br \/> <a href=\"#FILES\">FILES<\/a><br \/> <a href=\"#SEE ALSO\">SEE ALSO<\/a><br \/> <a href=\"#AUTHOR\">AUTHOR<\/a> <\/p>\n<hr>\n<h2>NAME <a name=\"NAME\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\">faillock.conf \u2212 pam_faillock configuration file<\/p>\n<h2>DESCRIPTION <a name=\"DESCRIPTION\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>faillock.conf<\/b> provides a way to configure the default settings for locking the user after multiple failed authentication attempts. This file is read by the <i>pam_faillock<\/i> module and is the preferred method over configuring <i>pam_faillock<\/i> directly.<\/p>\n<p style=\"margin-left:11%; margin-top: 1em\">The file has a very simple <i>name = value<\/i> format with possible comments starting with <i>#<\/i> character. The whitespace at the beginning of line, end of line, and around the <i>=<\/i> sign is ignored.<\/p>\n<h2>OPTIONS <a name=\"OPTIONS\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>dir=<\/b><i>\/path\/to\/tally\u2212directory<\/i><\/p>\n<p style=\"margin-left:17%;\">The directory where the user files with the failure records are kept. The default is \/var\/run\/faillock.<\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>audit<\/b><\/p>\n<p style=\"margin-left:17%;\">Will log the user name into the system log if the user is not found.<\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>silent<\/b><\/p>\n<p style=\"margin-left:17%;\">Don&#8217;t print informative messages to the user. Please note that when this option is not used there will be difference in the authentication behavior for users which exist on the system and non\u2212existing users.<\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>no_log_info<\/b><\/p>\n<p style=\"margin-left:17%;\">Don&#8217;t log informative messages via <b>syslog<\/b>(3).<\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>local_users_only<\/b><\/p>\n<p style=\"margin-left:17%;\">Only track failed user authentications attempts for local users in \/etc\/passwd and ignore centralized (AD, IdM, LDAP, etc.) users. The <b>faillock<\/b>(8) command will also no longer track user failed authentication attempts. Enabling this option will prevent a double\u2212lockout scenario where a user is locked out locally and in the centralized mechanism.<\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>deny=<\/b><i>n<\/i><\/p>\n<p style=\"margin-left:17%;\">Deny access if the number of consecutive authentication failures for this user during the recent interval exceeds <i>n<\/i>. The default is 3.<\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>fail_interval=<\/b><i>n<\/i><\/p>\n<p style=\"margin-left:17%;\">The length of the interval during which the consecutive authentication failures must happen for the user account lock out is <i>n<\/i> seconds. The default is 900 (15 minutes).<\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>unlock_time=<\/b><i>n<\/i><\/p>\n<p style=\"margin-left:17%;\">The access will be reenabled after <i>n<\/i> seconds after the lock out. The value 0 has the same meaning as value <i>never<\/i> \u2212 the access will not be reenabled without resetting the faillock entries by the <b>faillock<\/b>(8) command. The default is 600 (10 minutes).<\/p>\n<p style=\"margin-left:17%; margin-top: 1em\">Note that the default directory that <i>pam_faillock<\/i> uses is usually cleared on system boot so the access will be also reenabled after system reboot. If that is undesirable a different tally directory must be set with the <b>dir<\/b> option.<\/p>\n<p style=\"margin-left:17%; margin-top: 1em\">Also note that it is usually undesirable to permanently lock out the users as they can become easily a target of denial of service attack unless the usernames are random and kept secret to potential attackers.<\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>even_deny_root<\/b><\/p>\n<p style=\"margin-left:17%;\">Root account can become locked as well as regular accounts.<\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>root_unlock_time=<\/b><i>n<\/i><\/p>\n<p style=\"margin-left:17%;\">This option implies <b>even_deny_root<\/b> option. Allow access after <i>n<\/i> seconds to root account after the account is locked. In case the option is not specified the value is the same as of the <b>unlock_time<\/b> option.<\/p>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>admin_group=<\/b><i>name<\/i><\/p>\n<p style=\"margin-left:17%;\">If a group name is specified with this option, members of the group will be handled by this module the same as the root account (the options <b>even_deny_root<\/b> and <b>root_unlock_time<\/b> will apply to them. By default the option is not set.<\/p>\n<h2>EXAMPLES <a name=\"EXAMPLES\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\">\/etc\/security\/faillock.conf file example:<\/p>\n<p style=\"margin-left:17%; margin-top: 1em\">deny=4 <br \/> unlock_time=1200 <br \/> silent<\/p>\n<h2>FILES <a name=\"FILES\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\">\/etc\/security\/faillock.conf<\/p>\n<p style=\"margin-left:17%;\">the config file for custom options<\/p>\n<h2>SEE ALSO <a name=\"SEE ALSO\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>faillock<\/b>(8), <b>pam_faillock<\/b>(8), <b>pam.conf<\/b>(5), <b>pam.d<\/b>(5), <b>pam<\/b>(8)<\/p>\n<h2>AUTHOR <a name=\"AUTHOR\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\">pam_faillock was written by Tomas Mraz. The support for faillock.conf was written by Brian Ward.<\/p>\n<hr>\n","protected":false},"excerpt":{"rendered":"<p>  faillock.conf \u2212 pam_faillock configuration file <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[959],"tags":[961,841,1291],"class_list":["post-4740","post","type-post","status-publish","format-standard","hentry","category-5-formatos-de-ficheros","tag-961","tag-faillock","tag-man5"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4740","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=4740"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4740\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=4740"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=4740"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=4740"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}