From owner-freebsd-questions Sat May 27 06:09:24 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA21935 for questions-outgoing; Sat, 27 May 1995 06:09:24 -0700 Received: from sirius.brunel.ac.uk (root@sirius.brunel.ac.uk [134.83.128.62]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id GAA21917 for ; Sat, 27 May 1995 06:09:00 -0700 Received: from mishmash.brunel.ac.uk by sirius.brunel.ac.uk with SMTP (PP) id <06950-0@sirius.brunel.ac.uk>; Sat, 27 May 1995 14:08:53 +0100 From: Nik Clayton Message-Id: <862.9505271308@mishmash.brunel.ac.uk> Subject: Re: xlock To: allynh@avsi.com (Allyn Hardyck) Date: Sat, 27 May 1995 14:08:50 +0100 (BST) Cc: freebsd-questions@FreeBSD.org In-Reply-To: <199505262155.RAA13146@jupiter.avsi.com> from "Allyn Hardyck" at May 26, 95 05:55:02 pm X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 680 Sender: questions-owner@FreeBSD.org Precedence: bulk > Has there been a port made of xlock that uses the new passwd form? Last time this came up, the solution seemed to be to ensure that xlock is made setuid root[1]. This allows it to access the password file and get the real information, rather than the shadow information normally returned (try 'cat /etc/passwd' as a regular user, you'll see all the passwords are '*'d out). I think the latest version of xlock is "xlockmore-2.7.tar". Make sure you've got this one or later as well. N [1] % chmod 4755 /path/to/xlock/xlock =-[Opinion, n: See the above text for an example]=-=[Kibo #: e]-[RYRYRY]=-= =-[The Silly Sod Society: To perfect and to swerve]=-[beable]-=[TP U BG]=-=