From owner-freebsd-current@FreeBSD.ORG Wed Dec 3 11:52:28 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 5009316A4CE for ; Wed, 3 Dec 2003 11:52:28 -0800 (PST) Received: from web14106.mail.yahoo.com (web14106.mail.yahoo.com [216.136.172.136]) by mx1.FreeBSD.org (Postfix) with SMTP id 9794D43FDF for ; Wed, 3 Dec 2003 11:52:27 -0800 (PST) (envelope-from galen_sampson@yahoo.com) Message-ID: <20031203195227.17023.qmail@web14106.mail.yahoo.com> Received: from [67.122.109.97] by web14106.mail.yahoo.com via HTTP; Wed, 03 Dec 2003 11:52:27 PST Date: Wed, 3 Dec 2003 11:52:27 -0800 (PST) From: Galen Sampson To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: "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:52:28 -0000 Hello all, I have installed the MIT krb5 port. I installed this port and left KRB5_HOME=/usr/local (this is where I installed the port) in make.conf. I assumed that building the world would use this variable and link the world (ssh[d], telnet[d], login, ...) against the libraries installed by the port. That didn't seem to happen. I didn't want to define MAKE_KERBEROS5 in make.conf because I already installed the port and I thought that defining MAKE_KERBEROS5 would overwrite some of the port. 1) Are the worlds daemons written to link against kerberos (as apposed to the heimdal replacements replacing their traditional counterparts)? 2) If 1), is there a way to link the world against the port? If so, how? 3) If 2) is possible, is it a bad idea? 4) Are people that use the MIT kerberos port replacing their daemons (telnet [d], login, ftp[d]) with the ports versions with good success? 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). Regards, Galen Sampson __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/