From owner-cvs-all Sat Jan 23 18:40:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24707 for cvs-all-outgoing; Sat, 23 Jan 1999 18:40:06 -0800 (PST) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24576; Sat, 23 Jan 1999 18:39:59 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id KAA01228; Sun, 24 Jan 1999 10:16:28 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901240216.KAA01228@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki cc: Mark Murray , Sheldon Hearn , brandon@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: New crypt code is not sucessful In-reply-to: Your message of "Sun, 24 Jan 1999 03:04:36 +0100." Date: Sun, 24 Jan 1999 10:16:28 +0800 From: Peter Wemm Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk Andrzej Bialecki wrote: > On Sun, 24 Jan 1999, Peter Wemm wrote: > > > Speaking of rehashing.. I wonder what the chances of having the password > > verification stages of login (or PAM) rehashing the passwords on a > > successful login would be? > > If I'm not mistaken, it's only a matter of writing a PAM module that would > do this. As I understand it, it has to be done by the module that actually asked for and got the password. Adding an extra module in the sequence would (I believe) mean that it would have to ask for the password again.. I think.. It depends on whether there is any caching, and at what level the cache is held. > Andrzej Bialecki Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message