Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pam_permit(8) [freebsd man page]

PAM_PERMIT(8)						    BSD System Manager's Manual 					     PAM_PERMIT(8)

pam_permit -- Promiscuous PAM module SYNOPSIS
[service-name] module-type control-flag pam_permit [options] DESCRIPTION
The Promiscuous authentication service module for PAM, pam_permit provides functionality for all the PAM categories: authentication, account management, session management and password management. In terms of the module-type parameter, these are the ``auth'', ``account'', ``session'', and ``password'' features. The Promiscuous module will universally allow all requests. It is primarily of use during testing, and to silence ``noisy'' PAM-enabled applications. The following options may be passed to the module: debug syslog(3) debugging information at LOG_DEBUG level. SEE ALSO
syslog(3), pam.conf(5), pam(8) BSD
July 7, 2001 BSD

Check Out this Related Man Page

PAM_SECURETTY(8)					    BSD System Manager's Manual 					  PAM_SECURETTY(8)

pam_securetty -- SecureTTY PAM module SYNOPSIS
[service-name] module-type control-flag pam_securetty [options] DESCRIPTION
The SecureTTY service module for PAM, pam_securetty provides functionality for only one PAM category: account management. In terms of the module-type parameter, this is the ``account'' feature. It also provides null functions for authentication and session management. SecureTTY Account Management Module The SecureTTY account management component (pam_sm_acct_mgmt()), returns failure if the user is attempting to authenticate as superuser, and the process is attached to an insecure TTY. In all other cases, the module returns success. A TTY is considered secure if it is listed in /etc/ttys and has the TTY_SECURE flag set. The following options may be passed to the authentication module: debug syslog(3) debugging information at LOG_DEBUG level. no_warn suppress warning messages to the user. These messages include reasons why the user's authentication attempt was declined. SEE ALSO
getttynam(3), syslog(3), pam.conf(5), ttys(5), pam(8) BSD
July 8, 2001 BSD
Man Page

15 More Discussions You Might Find Interesting

1. Red Hat

Account lockout policy

Hi all; I m using Red Hat Enterprise Linux Server release 5.1 (Tikanga) and I'm trying to setup password lockout policy so that a user account locks out after 3 failed attempts. Here are the entires of my /etc/pam.d/system-auth #%PAM-1.0 # This file is auto-generated. # User changes... (1 Reply)
Discussion started by: maverick_here
1 Replies

2. UNIX for Dummies Questions & Answers

How to implement password policies?

How would i ensure that whenever any user changes the password it should meet following. It should be more than 7 Characters. Atleast one Upper case character,digit and special character present. Password is not same as username or dictionary word . User should get email after changing his... (2 Replies)
Discussion started by: pinga123
2 Replies

3. UNIX for Advanced & Expert Users

PAM authentication.

I have applied pam authentication for local users as highlighted in below file. # cat /etc/pam.d/system-auth #%PAM-1.0 # This file is auto-generated. # User changes will be destroyed the next time authconfig is run. auth required auth sufficient (0 Replies)
Discussion started by: pinga123
0 Replies

4. UNIX for Advanced & Expert Users

LDAP client issue

Hello, I'm new to Centos and to openldap. I am by trade a Solaris Admin. I'm experimenting with openldap and thought Linux would be easier to install and setup openldap on, so far this is true. The problem I'm having is that I can't get the client server to authenticate to the openldap server. I... (1 Reply)
Discussion started by: bitlord
1 Replies

5. UNIX for Advanced & Expert Users

psswd&shadow 2 passwd together?!!

hi, all I just started on new box where I have to diff passwd working perfectly on the very same account/user. I see that shadow was added recently (I'm not a root in there), I see 'x' in passwd. Not sure how it should work, should I change old passwd for one defined in shadow? Or it's fine to... (20 Replies)
Discussion started by: trento17
20 Replies

6. Red Hat

Account Lockout on Redhat

On a redhat linux 4 server, how to find if there is an account lockout duration is set. Is it configured under pam or /etc/shadow? what entries I need to find out? Is it module? I desperately need an answer because on one of the servers, no one was able to login through any account... (4 Replies)
Discussion started by: Tirmazi
4 Replies

7. Red Hat

Winbind and pam - restrict all services except for samba access

Hi, I have recently taken control of a number of RHEL5.3 servers that have samba shares setup on them and are authenticating using pam and winbind. My issue is that any user that has an active directory account can currently log in to the linux boxes using their ad credentials. I need to... (0 Replies)
Discussion started by: klyne
0 Replies

8. Linux

User Account Policy

Hi, i have the following config in the system-auth files auth required /lib/security/$ISA/ auth sufficient /lib/security/$ISA/ likeauth nullok auth required /lib/security/$ISA/ account required ... (2 Replies)
Discussion started by: yprudent
2 Replies

9. Red Hat

SSH not working

Hi, I have a server running RHEL 6.0. While logging in through root ,I can login.But if I try to login through "integ" user,I am unable to login. /var/log/secure messages::: May 20 15:25:23 punsyncserv su: pam_unix(su-l:session): session opened for user integ by root(uid=0) May 20 15:29:44... (4 Replies)
Discussion started by: nowornever
4 Replies

10. Red Hat

RHEL 6, incorrect logins, never lock.

i've been searching the WEB, and editing my /etc/pam.d/system-auth,passwd-auth,sshd. but even a thousand wrong logins, my account doesnt lock. thanks # cat system-auth-ac #%PAM-1.0 # This file is auto-generated. # User changes will be destroyed the next time authconfig is run. auth ... (2 Replies)
Discussion started by: invinzin21
2 Replies

11. OS X (Apple)

OSX and Kerberos

Our Network Security folks have mandated that we "Kerberize" our systems to allow them to perform an authenticated scan. This consists of instructions to change /etc/pam.d/sshd from: # sshd: auth account password session auth optional use_kcminit auth optional ... (0 Replies)
Discussion started by: jnojr
0 Replies

12. Gentoo

LDAP-Auth does not work correctly with systemd

Hi, since the upgrade to Gnome 3.6 (now i have 3.8) the authentication over LDAP stops working. The whole machine does not start anymore. The machine boot, but no gdm and no X. I can login, with root, but then the tty hangs. When i look at ttyF12 i see a lot of systemd service the runs random,... (1 Reply)
Discussion started by: darktux
1 Replies

13. Red Hat

Password policy for root

Hi, I am unable to enforce password complexity policy for root user. (other users are working) on RHEL 6.2. Anything wrong with system-auth parameters? PLease help.. vi /etc/pam.d/system-auth #%PAM-1.0 # This file is auto-generated. # User changes will be destroyed the next time... (1 Reply)
Discussion started by: suresh3566
1 Replies

14. Linux

User can't "su -" to root

Hello. I have a RHEL 7.2 where a regular user can't make a "su -" to reach root account: server532:t711740:/$ id uid=75456(t711740) gid=10000(personales) groups=10000(personales),10(wheel) tehrh532:t711740:/$ su - Password: su: Permission denied But can make "sudo su -"... (2 Replies)
Discussion started by: Gabriander
2 Replies

15. UNIX for Advanced & Expert Users

SOCKS proxy & PAM configuration exposure

I've got a problem with a proxy configuration. We have an LDAP group that lists all users who are authorised to use the proxy to FTP (usually Filezilla) out to the world, and by implication those not in the group should be denied. My users are delighted that this has been enabled and those that... (9 Replies)
Discussion started by: rbatte1
9 Replies