Bug 126819

Summary: default settings are insecure
Product: Red Hat Enterprise Linux 3 Reporter: Robert de Rooy <rderooy>
Component: xscreensaverAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0Keywords: Security
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:04:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Robert de Rooy 2004-06-27 21:54:43 UTC
Description of problem:

Security issues:
1) By default xscreensaver only runs as a regular user, not root
2) xscreensaver does not lock the screen by default
3) screensaver might reveal personal information

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Install any RHL or Fedora release with xwindows
2. 
3.
  
Actual results:


Expected results:

1) although logging into X as root should be discouraged, not allowing
the display to be locked is simply crazy. Root should be able to lock
his display, preferably just with a blank screen option and not the
gazilion others that *might* have a security issue.

2) a default install of RHL or Fedora does not lock the display when
the screensaver activates. Default settings should be changed so the
display gets locked after 5 or 10 min. If the user does not wish for
his display to get locked, he can disable it. Security should be the
default, not the other way around.

3) default screensaver selection might reveal personal information on
the users desktop when the screensaver was activated, or contained in
files on the harddisk. Default screensaver selection should be such
that NO personal or system information is revealed.

Additional info:

Comment 1 Suzanne Hillman 2004-07-08 20:06:13 UTC

*** This bug has been marked as a duplicate of 126809 ***

Comment 2 Red Hat Bugzilla 2006-02-21 19:04:14 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.