From owner-freebsd-current Sun Oct 4 11:11:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04746 for freebsd-current-outgoing; Sun, 4 Oct 1998 11:11:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04683; Sun, 4 Oct 1998 11:11:23 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id LAA07861; Sun, 4 Oct 1998 11:10:51 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Mark Murray cc: markm@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Problems with Kerberos and /etc/auth.conf In-reply-to: Your message of "Sun, 04 Oct 1998 19:59:49 +0200." <199810041759.TAA06181@gratis.grondar.za> Date: Sun, 04 Oct 1998 11:10:51 -0700 Message-ID: <7857.907524651@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How about a "deKerberise" target in src/kerberosIV (or wherever)? I'm > sure I can bang one into shape. That would only help those who got into that position through builds, there being a lot more who simply check everything in the "DES" menu in sysinstall and don't have sources. Besides, it seems like it would be nifty to not _eliminate_ the Kerberos abilities so much as simply disabling them on demand. If su sees that kerberos authentication is not enabled on the system, for example, it just treats it like an implicit -K. I have no problem with implementing an auth.conf parser and the routines to query its state, if that would help. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message