Bug 51686
Summary: | default for xscreensaver app-defaults should be lock | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | Seth Vidal <skvidal> |
Component: | xscreensaver | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | roswell | CC: | jwz, rvokal |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-07-27 11:58: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
Seth Vidal
2001-08-13 20:58:03 UTC
It would be crazy to turn on locking by default. Why would it be crazy? This is not something where I'd think we'd deviate from a) upstream b) established behavior. 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. |