4 This file was written by Andrew G. Morgan <morgan@kernel.org>
7 <sect1>The promiscuous module
14 <tag><bf>Module Name:</bf></tag>
17 <tag><bf>Author:</bf></tag>
18 Andrew G. Morgan, <morgan@kernel.org>
20 <tag><bf>Maintainer:</bf></tag>
23 <tag><bf>Management groups provided:</bf></tag>
24 account; authentication; password; session
26 <tag><bf>Cryptographically sensitive:</bf></tag>
28 <tag><bf>Security rating:</bf></tag>
29 VERY LOW. Use with extreme caution.
31 <tag><bf>Clean code base:</bf></tag>
34 <tag><bf>System dependencies:</bf></tag>
36 <tag><bf>Network aware:</bf></tag>
40 <sect2>Overview of module
43 This module is very dangerous. It should be used with extreme
44 caution. Its action is always to permit access. It does nothing else.
46 <sect2>Account+Authentication+Password+Session components
51 <tag><bf>Recognized arguments:</bf></tag>
53 <tag><bf>Description:</bf></tag>
55 No matter what management group, the action of this module is to
56 simply return <tt/PAM_SUCCESS/ -- operation successful.
59 In the case of authentication, the user's name will be acquired. Many
60 applications become confused if this name is unknown.
62 <tag><bf>Examples/suggested usage:</bf></tag>
64 It is seldom a good idea to use this module. However, it does have
65 some legitimate uses. For example, if the system-administrator wishes
66 to turn off the account management on a workstation, and at the same
67 time continue to allow logins, then she might use the following
68 configuration file entry for login:
72 # add this line to your other login entries to disable account
73 # management, but continue to permit users to log in...
75 login account required pam_permit.so
82 End of sgml insert for this module.