From efd31890b5ed496a5a00c08a262da240e66a4ddc Mon Sep 17 00:00:00 2001 From: Steve Langasek Date: Thu, 3 Jan 2019 12:44:11 -0800 Subject: New upstream version 0.76 --- doc/modules/pam_permit.sgml | 83 --------------------------------------------- 1 file changed, 83 deletions(-) delete mode 100644 doc/modules/pam_permit.sgml (limited to 'doc/modules/pam_permit.sgml') diff --git a/doc/modules/pam_permit.sgml b/doc/modules/pam_permit.sgml deleted file mode 100644 index fe616ac3..00000000 --- a/doc/modules/pam_permit.sgml +++ /dev/null @@ -1,83 +0,0 @@ - - -The promiscuous module - -Synopsis - -

- - -Module Name: -pam_permit - -Author: -Andrew G. Morgan, <morgan@kernel.org> - -Maintainer: -Linux-PAM maintainer. - -Management groups provided: -account; authentication; password; session - -Cryptographically sensitive: - -Security rating: -VERY LOW. Use with extreme caution. - -Clean code base: -Clean. - -System dependencies: - -Network aware: - - - -Overview of module - -

-This module is very dangerous. It should be used with extreme -caution. Its action is always to permit access. It does nothing else. - -Account+Authentication+Password+Session components - -

- - -Recognized arguments: - -Description: - -No matter what management group, the action of this module is to -simply return -In the case of authentication, the user's name will be acquired. Many -applications become confused if this name is unknown. - -Examples/suggested usage: - -It is seldom a good idea to use this module. However, it does have -some legitimate uses. For example, if the system-administrator wishes -to turn off the account management on a workstation, and at the same -time continue to allow logins, then she might use the following -configuration file entry for login: - - -# -# add this line to your other login entries to disable account -# management, but continue to permit users to log in... -# -login account required pam_permit.so - - - - - - -- cgit v1.2.3