search for: pam_converse

Hi, My company decided to implement security restrictions lately and I was to write more strict authorization modules for pam. One of it works asking for some kind of additional security string (for example pin from some kind of token). It is done by pam module, which asks calling application to do conversation for him: prompt_msg.msg_style = PAM_PROMPT_ECHO_OFF;

SecureComputing's PAM library doesn't pass back the correct context to the pam_conversation function, i.e. it passes back NULL. So this patch works around this fact. likely you'll only want this hack if you expect to use pam_safeword.so in your authentication check, and only if you run sshd in privilege separation (separate process) mode so that the PAM conversation is single

I'm using Samba 220, Solaris 2.8/Sparc, Sun Forte C Compiler. I ran ./configure using --with-pam so I could use winbind. During compilation, I get the following warning messages: ............ Compiling passdb/secrets.c Compiling passdb/pass_check.c "passdb/pass_check.c", line 671: warning: statement not reached Compiling passdb/ldap.c Compiling passdb/nispass.c Compiling