From owner-freebsd-current Tue Oct 6 06:31:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA16014 for freebsd-current-outgoing; Tue, 6 Oct 1998 06:31:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bg.sics.se (bg.sics.se [193.10.66.124]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA16007; Tue, 6 Oct 1998 06:31:14 -0700 (PDT) (envelope-from bg@bg.sics.se) Received: (from bg@localhost) by bg.sics.se (8.8.5/8.8.5) id PAA07458; Tue, 6 Oct 1998 15:31:20 +0200 (CEST) To: "Jordan K. Hubbard" Cc: markm@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Problems with Kerberos and /etc/auth.conf References: <7633.907521782@time.cdrom.com> From: Bjoern Groenvall Date: 06 Oct 1998 15:31:20 +0200 In-Reply-To: "Jordan K. Hubbard"'s message of Sun, 04 Oct 1998 10:23:02 -0700 Message-ID: Lines: 32 X-Mailer: Red Gnus v0.52/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > OK, so I'm just going down my sheet of "things that various people > have reported as being most annoying in FreeBSD" and I'm looking at > the 'ol "su -K" FAQ, that being the one where people inadvertently > install kerberos (either by checking too many things off an install > menu or building from sources) and it subsequently bites the > non-internet connected by making su pause for a heck of a long time > trying to contact a kerberos server which doesn't exist. The > work-around is to use the -K flag, of course, but this apparently > remains a well-kept secret despite having been mentioned many times on > USENET and other forums, and people are basically putting their feet > into this rabbit hole. We need to do something! :-) A simple medicine for this problem can be found in the krb4 source crypto/kerberosIV/appl/bsd/su.c, i.e the su program that is not built. if (use_kerberos) { int fd = open (KEYFILE, O_RDONLY); if (fd >= 0) close (fd); else use_kerberos = 0; } Cheers, Björn PS Are there any other situations where kerberized programs are known to hang? DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message