Date: Thu, 25 Feb 1999 16:30:29 -0500 From: Brian Cully <shmit@kublai.com> To: Chris Shenton <cshenton@uucom.com> Cc: mike@seidata.com, GVB <gvbmail@tns.net>, freebsd-net@FreeBSD.ORG Subject: Re: RADIUS Solutions Message-ID: <19990225163029.E10052@kublai.com> In-Reply-To: <86d82ytcbu.fsf@samizdat.uucom.com>; from Chris Shenton on Thu, Feb 25, 1999 at 04:15:01PM -0500 References: <19990223192031.C50175@kublai.com> <Pine.BSF.4.05.9902250233010.25461-100000@ns1.seidata.com> <19990225123427.C10052@kublai.com> <86d82ytcbu.fsf@samizdat.uucom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 25, 1999 at 04:15:01PM -0500, Chris Shenton wrote: > Won't this lose if the user exists in the cached password file but the > password is wrong, e.g., if the user changed it on the master copy? > I'd think you'd have synchronization problems.... > > Or do you push the change out when it occurs, like when the user > changes his password? And not push the entire password file? Or > something else? I was leaving that part out to avoid confusion. :-) When a user changes his password, we send out an invalidation packet to the RADIUS servers that tells them to re-sync this user's password with the one from the master. -bjc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990225163029.E10052>