RE: [SLE] pam.d login file configuration question
Hi I'm busy playing around with PAM at the moment on my servers. I found a couple of README files on the various modules as well as some documents on PAM Administration on my server. Take a look here: /usr/share/doc/packages/pam /usr/share/doc/packages/pam/modules Hope this helps. Stephen -----Original Message----- From: daniel parkes [mailto:liquidsmail@gmail.com] Sent: 31 August 2005 11:53 AM To: suse-linux-e@suse.com Subject: [SLE] pam.d login file configuration question Hy people, I am having a look at a configured pam login file, and i cant find enough information to understand what it all means, if any of you would be so kind to explain any line of the file that i paste: auth requisite pam_unix2.so nullok #set_secrpc auth required pam_securetty.so auth required pam_nologin.so #auth required pam_homecheck.so auth required pam_env.so auth required pam_mail.so account required pam_unix2.so password required pam_pwcheck.so nullok password required pam_unix2.so nullok use_first_pass use_authtok session required pam_unix2.so none # debug or trace session required pam_limits.so session optional pam_laus.so auth required /lib/security/pam_tally.so onerr=fail no_magic_root account required /lib/security/pam_tally.so deny=10 reset no_magic_root If u could also point me out some links that explain in detail the pam files configuration, i cant find anything usefull on the net. Thnx a LoT!!!!. Cya. Disclaimer "Everything in this e-mail and attachments relating to the official business of Medscheme Holdings ( Pty ) Ltd ( Reg Number 1970/015014/07 ) is proprietary to the company. It is confidential, legally privileged and protected by law. Medscheme Holdings does not own and endorse any other content. Views and opinions are those of the sender unless clearly stated as being that of Medscheme Holdings. The person addressed in the e-mail is the sole authorised recipient. Please notify the sender immediately if it has unintentionally reached you and do not read, disclose or use the content in any way. Whilst all reasonable steps are taken to ensure the accuracy and integrity of information and data transmitted electronically and to preserve the confidentiality thereof, no liability or responsibility whatsoever is accepted if information or data is,for whatever reason, corrupted or does not reach its intended destination."
participants (1)
-
Stephen Hughes