From owner-freebsd-questions Thu Jun 1 11:18:53 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA00104 for questions-outgoing; Thu, 1 Jun 1995 11:18:53 -0700 Received: from cancer.ibms.sinica.edu.tw ([140.109.40.250]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA29993 for ; Thu, 1 Jun 1995 11:18:46 -0700 Received: (from taob@localhost) by cancer.ibms.sinica.edu.tw (8.6.11/8.6.9) id CAA02818; Fri, 2 Jun 1995 02:18:11 +0800 Date: Fri, 2 Jun 1995 02:18:10 +0800 (CST) From: Brian Tao To: Tony Harverson cc: freebsd-questions@FreeBSD.org Subject: Re: Xlock ? In-Reply-To: <199506010938.LAA04519@beastie.cs.und.ac.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: questions-owner@FreeBSD.org Precedence: bulk On Thu, 1 Jun 1995, Tony Harverson wrote: > > I just got X running on our host here and got hold of the xlockmore1.4 that > was available under the 2.0 distribution as a package. It installed > without a problem, and runs nicely, but when I provide it with my password > to unlock, I get an invalid login message. (FreeBSD 2.0R - X 3.1) Is this > a known problem ? What is the solution ? Probably need to set the xlockmore binary to setuid root (so it can read the shadow password file). Xlockmore 1.4? The current version is 2.9!!! I grabbed that about a week ago and it compiles straight away for FreeBSD (including the setuid part). -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org