blob: 8ddc2bbe331f8b6f910c7bf8fdf2a80a48401e7b [file] [log] [blame]
paul788cdc62003-01-18 00:22:08 +00001#%PAM-1.0
2#
pauledd7c242003-06-04 13:59:38 +00003
paul5f5eab72003-08-12 12:56:00 +00004##### if running quagga as root:
paul788cdc62003-01-18 00:22:08 +00005# Only allow root (and possibly wheel) to use this because enable access
6# is unrestricted.
paul074a9172004-06-06 10:27:53 +00007auth sufficient /lib/security/$ISA/pam_rootok.so
paul788cdc62003-01-18 00:22:08 +00008
paul788cdc62003-01-18 00:22:08 +00009# Uncomment the following line to implicitly trust users in the "wheel" group.
paul074a9172004-06-06 10:27:53 +000010#auth sufficient /lib/security/$ISA/pam_wheel.so trust use_uid
paul788cdc62003-01-18 00:22:08 +000011# Uncomment the following line to require a user to be in the "wheel" group.
paul074a9172004-06-06 10:27:53 +000012#auth required /lib/security/$ISA/pam_wheel.so use_uid
pauledd7c242003-06-04 13:59:38 +000013###########################################################
14
paul5f5eab72003-08-12 12:56:00 +000015# If using quagga privileges and with a seperate group for vty access, then
pauledd7c242003-06-04 13:59:38 +000016# access can be controlled via the vty access group, and pam can simply
paul2f4453f2003-08-13 06:05:01 +000017# check for valid user/password, eg:
pauledd7c242003-06-04 13:59:38 +000018#
19# only allow local users.
paul074a9172004-06-06 10:27:53 +000020#auth required /lib/security/$ISA/pam_securetty.so
21#auth required /lib/security/$ISA/pam_stack.so service=system-auth
22#auth required /lib/security/$ISA/pam_nologin.so
23#account required /lib/security/$ISA/pam_stack.so service=system-auth
24#password required /lib/security/$ISA/pam_stack.so service=system-auth
25#session required /lib/security/$ISA/pam_stack.so service=system-auth
26#session optional /lib/security/$ISA/pam_console.so