NetBSD Problem Report #10336
Received: (qmail 6493 invoked from network); 10 Jun 2000 12:23:08 -0000
Message-Id: <200006101223.e5ACN7f18344@acheron.middleboro.ma.us>
Date: Sat, 10 Jun 2000 08:23:07 -0400 (EDT)
From: mason@acheron.middleboro.ma.us
Reply-To: mason@acheron.middleboro.ma.us
To: gnats-bugs@gnats.netbsd.org
Subject: xlock really badly broken...
X-Send-Pr-Version: 3.95
>Number: 10336
>Category: pkg
>Synopsis: xlock really badly broken...
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: pkg-manager
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sat Jun 10 12:24:00 +0000 2000
>Closed-Date: Mon Jul 17 15:12:59 +0000 2000
>Last-Modified: Sun Dec 17 13:36:16 +0000 2000
>Originator: Mason Loring Bliss
>Release: xlockmore-4.16.1
>Organization:
>Environment:
System: NetBSD acheron.middleboro.ma.us 1.4ZB NetBSD 1.4ZB (MLB) #18: Thu Jun 8 14:36:35 EDT 2000 root@acheron.middleboro.ma.us:/usr/src/sys/arch/i386/compile/MLB i386
>Description:
With my current system, xlockmore will prompt me for a passphrase. If that
passphrase is correct, it will let me in. If that passphrase is incorrect,
it will tell me "Invalid login." ... and let me in.
While my network uses NIS, this is on my master NIS server, and thus should
be doing normal, local password lookups.
>How-To-Repeat:
Build xlockmore, lock screen, test. This may be due to some quirk on my
own machine, but on this machine, at least, it's 100% reproducible and
consistent.
>Fix:
As yet unknown.
>Release-Note:
>Audit-Trail:
From: Hubert Feyrer <feyrer@rfhs8012.fh-regensburg.de>
To: mason@acheron.middleboro.ma.us
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: pkg/10336: xlock really badly broken...
Date: Mon, 17 Jul 2000 16:49:36 +0200 (MET DST)
On Sat, 10 Jun 2000 mason@acheron.middleboro.ma.us wrote:
> Build xlockmore, lock screen, test. This may be due to some quirk on my
> own machine, but on this machine, at least, it's 100% reproducible and
> consistent.
I've just done a "make install" on a 1.5_ALPHA machine, started "xlock",
and I was *not* able to reproduce this.
Maybe this has to do with NIS?
What's the permissions on your xlock binary?
What does your /etc/nsswitch.conf look like?
Can you telnet into the box?
- Hubert
--
NetBSD - because Unix isn't just #include <linux.h>, i386, ILP32, ELF, ...!
State-Changed-From-To: open->closed
State-Changed-By: hubertf
State-Changed-When: Mon Jul 17 08:12:20 PDT 2000
State-Changed-Why:
Noone knows where this came from, and the submitter can't reproduce
it any more. Close
- Hubert
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.