Date: Tue, 14 Mar 2006 15:17:46 +0100 From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: "Mr CW" <mrcomputerwiz@hotmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: freebsd-hackers Digest, Vol 156, Issue 2 Message-ID: <86mzftf6ut.fsf@xps.des.no> In-Reply-To: <BAY102-F13D394339B96D308122E80B3E10@phx.gbl> (mrcomputerwiz@hotmail.com's message of "Tue, 14 Mar 2006 13:30:48 %2B0000") References: <BAY102-F13D394339B96D308122E80B3E10@phx.gbl>
next in thread | previous in thread | raw e-mail | index | archive | help
"Mr CW" <mrcomputerwiz@hotmail.com> writes: > My appologies and thank you for pointing out my error. I have been > walking the source tree trying to find out how different programs > work and, I'll admit, passwd is one of the first few programs. I > had believed that pam_get_authtok.c was tied into passwd through the > many different includes in the program tree. Specifically, I want > to learn how passwd works from the point where it prompts for the > password, where it actually receives the input, how it passes the > password off for encryption, and when it finally obtains the > encrypted value. It uses PAM. Start by reading the following: <URL:http://www.freebsd.org/doc/en/articles/pam/>; > The lower portion of ...get_authtok.c appeared to me where this > happens, when the response is stored in &resp, retyped into &resp2 > to ensure the two are the same, then sent to pam_set_item() for > encryption (?). No, pam_set_item() merely stores the password in the PAM context. > The way I am reading it, &resp points to the unencrypted password > string, but I could be wrong. That is correct. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86mzftf6ut.fsf>