From owner-freebsd-hackers@FreeBSD.ORG Tue Mar 14 14:17:54 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE88916A401 for ; Tue, 14 Mar 2006 14:17:54 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B88F43D48 for ; Tue, 14 Mar 2006 14:17:54 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 49835208E; Tue, 14 Mar 2006 15:17:47 +0100 (CET) X-Spam-Tests: AWL,BAYES_00,FORGED_RCVD_HELO X-Spam-Learn: ham X-Spam-Score: -2.4/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id CA8752086; Tue, 14 Mar 2006 15:17:46 +0100 (CET) Received: by xps.des.no (Postfix, from userid 1001) id B0D1E33C8D; Tue, 14 Mar 2006 15:17:46 +0100 (CET) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: "Mr CW" References: Date: Tue, 14 Mar 2006 15:17:46 +0100 In-Reply-To: (mrcomputerwiz@hotmail.com's message of "Tue, 14 Mar 2006 13:30:48 +0000") Message-ID: <86mzftf6ut.fsf@xps.des.no> User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: freebsd-hackers Digest, Vol 156, Issue 2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 14:17:54 -0000 "Mr CW" 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: > 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