Bug 51686 - default for xscreensaver app-defaults should be lock
Summary: default for xscreensaver app-defaults should be lock
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: xscreensaver   
(Show other bugs)
Version: roswell
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
Keywords: FutureFeature
Depends On:
TreeView+ depends on / blocked
Reported: 2001-08-13 20:58 UTC by Seth Vidal
Modified: 2014-03-17 02:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-07-27 11:58:14 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Seth Vidal 2001-08-13 20:58:03 UTC
Description of Problem:

This is silly but it would be nice if the default for xscreensaver would be
to lock.

You can easily do this by editing the XScreenSaver file in

if you change:
*lock: False 
*lock: True

then it should lock by default.

yes. I know I can do this in the post installs of my systems but I think
its 1. an easy change and 2. a good security feature for it to be on by

Comment 1 Jamie Zawinski 2002-07-27 06:43:27 UTC
It would be crazy to turn on locking by default.

Comment 2 Seth Vidal 2002-07-27 11:58:09 UTC
Why would it be crazy?

Comment 3 Bill Nottingham 2002-08-13 01:29:45 UTC
This is not something where I'd think we'd deviate from a) upstream b)
established behavior.

Comment 4 Seth Vidal 2002-08-13 01:36:13 UTC
established behavior is ipchains/iptables are not enabled - y'all have them
enabled in the installer by default, why do you do this? b/c it makes the system
more secure - the same is true for locking on the screensaver.

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