From owner-freebsd-current@FreeBSD.ORG Wed Dec 3 11:57:50 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CAC916A4CE for ; Wed, 3 Dec 2003 11:57:50 -0800 (PST) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEAFC43FB1 for ; Wed, 3 Dec 2003 11:57:48 -0800 (PST) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id 5BF6A124; Wed, 3 Dec 2003 13:57:48 -0600 (CST) Date: Wed, 3 Dec 2003 13:57:48 -0600 From: Tillman Hodgson To: current@freebsd.org Message-ID: <20031203195748.GK294@seekingfire.com> References: <20031203195227.17023.qmail@web14106.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031203195227.17023.qmail@web14106.mail.yahoo.com> X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers User-Agent: Mutt/1.5.5.1i Subject: Re: "The World" and MIT krb5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2003 19:57:50 -0000 On Wed, Dec 03, 2003 at 11:52:27AM -0800, Galen Sampson wrote: > Hello all, [Note: I'm not sure that this should be in current@ rather than ports@] > 1) Are the worlds daemons written to link against kerberos (as apposed to the > heimdal replacements replacing their traditional counterparts)? The MIT krb5 port includes it's own daemons. > 4) Are people that use the MIT kerberos port replacing their daemons (telnet > [d], login, ftp[d]) with the ports versions with good success? Yup. Or they're using the Heimdal daemons in the base system (as described in the handbook chapter on Kerberos 5). I prefer MIT myself, but that's largely because of unrelated benefits that may apply only in my situation. > I'd imagine that since the port is installed in /usr/local things might not > work so great if /usr/local can't be accessed (because of mount failure, etc.) > unless the daemons are statically linked (NO THIS IS NOT A THREAD ABOUT STATIC > LINKING, THIS IS AN OBSERVATION ABOUT THIS PORT AND A POSSIBLE ANSWER TO 3). I'm not sure what you're talking about here ... if the deamons are in /usr/local/, and the /usr/local isn't available, static linking isn't going to help :-) I tend to put them in /usr/local/krb5 so that I can control which application I get by default with creative $PATH ordering. -T -- >From empirical experience, your Exchange admin needs to put down the crack pipe and open a window to disperse the fumes. - A.S.R. quote (Joe Thompson)