From owner-freebsd-stable Fri Apr 3 14:58:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23102 for freebsd-stable-outgoing; Fri, 3 Apr 1998 14:58:00 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from fledge.watson.org (root@FLEDGE.RES.CMU.EDU [128.2.91.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23091 for ; Fri, 3 Apr 1998 14:57:45 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.6.10) with SMTP id RAA26769; Fri, 3 Apr 1998 17:57:30 -0500 (EST) Date: Fri, 3 Apr 1998 17:57:29 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Wes Peters - Softweyr LLC cc: stable@FreeBSD.ORG Subject: Re: Hesiod support on 2.2 In-Reply-To: <199804032219.PAA17773@xmission.xmission.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Fri, 3 Apr 1998, Wes Peters - Softweyr LLC wrote: > DNS wasn't really designed with a highly volatile dataset in mind. If > it takes a day or two for the existence of a new workstation to trickle > across the net, that's generally not too bad, but if it takes a day or > two for my new password to trickle across the net, I cannot reliably > predict if I can login or not. However, password support in Athena was designed to be distributed using Kerberos, not Hesiod. In a large system, a lag-time of a day for account creation across 5,000 workstations is not so bad. Robert N Watson ---- Carnegie Mellon University http://www.cmu.edu/ Trusted Information Systems http://www.tis.com/ SafePort Network Services http://www.safeport.com/ robert@fledge.watson.org http://www.watson.org/~robert/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message