Subject: pkg/10336: xlock really badly broken...
To: None <gnats-bugs@gnats.netbsd.org>
From: None <mason@acheron.middleboro.ma.us>
List: netbsd-bugs
Date: 06/10/2000 05:23:13
>Number:         10336
>Category:       pkg
>Synopsis:       xlock really badly broken...
>Confidential:   yes
>Severity:       critical
>Priority:       high
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jun 10 05:24:00 PDT 2000
>Closed-Date:
>Last-Modified:
>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:
>Unformatted: