From owner-freebsd-current Sat Oct 24 23:16:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10874 for freebsd-current-outgoing; Sat, 24 Oct 1998 23:16:51 -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 XAA10869 for ; Sat, 24 Oct 1998 23:16:50 -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 XAA10643; Sat, 24 Oct 1998 23:16:11 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Terry Lambert cc: john.saunders@scitec.com.au, freebsd-current@FreeBSD.ORG Subject: Re: [Q]: Buildworld without secure libs (to use MD5 passwords) In-reply-to: Your message of "Sat, 24 Oct 1998 22:42:15 -0000." <199810242242.PAA27859@usr01.primenet.com> Date: Sat, 24 Oct 1998 23:16:10 -0700 Message-ID: <10639.909296170@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > When you are a passenger headed for an unavoidable car wreck, it's > still nice to know that someone is steering. Cold comfort indeed, perhaps, to have anyone pretending to do anything effective in avoiding an unavoidable solution. ;) > Still, even if the new file must stay, it would be nice to know > that at least it was the result of someone is steering, instead > of being the result of people not communicating. "Dear Terry, we were here and we waited for you, but you didn't show up. What happened? Signed - Jordan & Mark" This _was_ discussed in -current. I raised the issue of disabling things like kerberos authentication for kerberized binaries and setting the default password time. Discussion ensued. Code was thrown indiscriminately around. Things evolved and Mark subsequently committed the kerberos knob. The password knob remains to follow. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message