PAM conversation stuff

Nicolas Williams Nicolas.Williams at ubsw.com
Fri Oct 26 23:38:06 EST 2001


See the Linux-PAM, XSSO and Sun PAM docs here:

http://www.kernel.org/pub/linux/libs/pam/

and here:

http://docs.sun.com/

Nico


On Thu, Oct 25, 2001 at 05:51:20PM -0400, Ed Phillips wrote:
> Okay, I'm confused again.  They way you guys are talking about the
> conversation routine, it would seem that you think it is a way to fetch
> something from the user - like a new password.  Is this possible?  Does
> calling pam_chauthtok() cause the underlying pam_sm_chauthtok()
> eventually print something on stdout and read a new password from stdin
> (the socket to the client) using the conversation routine?  If this is
> what is happening, then logically the bug is in the part of the
> conversation routine that isn't checking to see if stdin/stdout is a TTY
> before trying to prompt the user for info.
> 
> Conversely, the conversation routine is just a glorified "printf", then
> where in the heck is the password read in, and where is pam_set_item()
> being called to fill in the details before the call to pam_chauthtok() can
> actually update the password?
> 
> Thanks,
> 
> 	Ed
> 
> Ed Phillips <ed at udel.edu> University of Delaware (302) 831-6082
> Systems Programmer III, Network and Systems Services
> finger -l ed at polycut.nss.udel.edu for PGP public key
--
-DISCLAIMER: an automatically appended disclaimer may follow. By posting-
-to a public e-mail mailing list I hereby grant permission to distribute-
-and copy this message.-

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.




More information about the openssh-unix-dev mailing list