Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 4898 - Xscreensaver (NIS passwd's): Can still unlock screen w/ old passwd and new passwd after changing passwd with yppasswd
Summary: Xscreensaver (NIS passwd's): Can still unlock screen w/ old passwd and new pa...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: xscreensaver
Version: 6.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-09-03 21:54 UTC by pfeif
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 1999-09-03 22:49:59 UTC


Attachments (Terms of Use)

Description pfeif 1999-09-03 21:54:08 UTC
I'm running 6.0 with all updates applied, our passwd file is
distributed via NIS. After changing my passwd w/ yppasswd
and verifying that it works, I can still unlock my screen
with my old passwd and the new passwd. The old passwd does
not work for anything else except xscreensaver. I am running
nscd.

	Marc Heckmann

Comment 1 Bill Nottingham 1999-09-03 22:49:59 UTC
xscreensaver uses the NIS password in effect at the time
that the xscreensaver parent process was started  - normally
this is when you start your session.

From  the man page:

              If you change your password after xscreensaver has
               been  launched,  it  will  continue using your old
               password to unlock the screen  until  xscreensaver
               is restarted.  So, after you change your password,
               you'll have to do

                    xscreensaver-command -restart


Note You need to log in before you can comment on or make changes to this bug.