KGRKJGETMRETU895U-589TY5MIGM5JGB5SDFESFREWTGR54TY
Server : Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/0.9.8e-fips-rhel5 DAV/2 PHP/5.2.17
System : Linux localhost 2.6.18-419.el5 #1 SMP Fri Feb 24 22:47:42 UTC 2017 x86_64
User : nobody ( 99)
PHP Version : 5.2.17
Disable Function : NONE
Directory :  /proc/21573/root/usr/share/doc/pam-0.99.6.2/txts/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Current File : //proc/21573/root/usr/share/doc/pam-0.99.6.2/txts/README.pam_stack
This is pam_stack, a module for implementing recursive stacking with
Linux-PAM.  Because it's naughty and accesses some of the internals of
libpam, it's not likely that it can be made to work on anything but
Linux-PAM on Linux, FreeBSD, and other OSs that use Linux-PAM.

In a nutshell, calling pam_stack diverts a PAM stack into another
configuration file.  If the substack executes successfully, pam_stack
returns PAM_SUCCESS.  If the substack fails, pam_stack returns the
error code returned by the internal PAM dispatching routines, which
is typically the code returned by the module that failed.

This is primarily of use for when you want a consistent authentication
model for all of your system services, but want to allow the specifics
to change from service to service (like whether or not to use pam_rootok
or pam_securetty).

The module takes only two arguments:
debug		log lots of information to the system log
service=NAME	use as a substack the stack defined for the NAME service,
		usually the name of a file in /etc/pam.d

Nalin Dahyabhai <nalin@redhat.com>

Anon7 - 2021