From owner-freebsd-hackers Mon Nov 3 15:56:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA14548 for hackers-outgoing; Mon, 3 Nov 1997 15:56:10 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA14539 for ; Mon, 3 Nov 1997 15:56:04 -0800 (PST) (envelope-from sef@Kithrup.COM) Received: (from sef@localhost) by kithrup.com (8.8.5/8.6.6) id PAA07369; Mon, 3 Nov 1997 15:55:58 -0800 (PST) Date: Mon, 3 Nov 1997 15:55:58 -0800 (PST) From: Sean Eric Fagan Message-Id: <199711032355.PAA07369@kithrup.com> To: hackers@freebsd.org Reply-To: hackers@freebsd.org Subject: Re: Password verification (Was: cvs commit: ports/x11/kdebase - Imported sources) In-Reply-To: <199711032102.TAA09231.kithrup.freebsd.hackers@gaia.coppe.ufrj.br> References: from Tom at "Nov 3, 97 10:07:24 am" Organization: Kithrup Enterprises, Ltd. Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199711032102.TAA09231.kithrup.freebsd.hackers@gaia.coppe.ufrj.br> you write: >Or, maybe, that a GROUP of uids could see every other password. >It is a way of thinking, and may be useful too. The proper way to do this is with Kerberos. *duck* Okay, but kerberos does provide a usable model, and it's already in the system. It doesn't let you see the encrypted password, but it does let you check to see whether a password matches. (And it doesn't send the password out in clear-text over the wire, either.)