From owner-freebsd-bugs  Wed Apr  1 03:20:03 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id DAA06742
          for freebsd-bugs-outgoing; Wed, 1 Apr 1998 03:20:03 -0800 (PST)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id DAA06730;
          Wed, 1 Apr 1998 03:20:02 -0800 (PST)
          (envelope-from gnats)
Date: Wed, 1 Apr 1998 03:20:02 -0800 (PST)
Message-Id: <199804011120.DAA06730@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: Don Morrison <dmorrisn@u.washington.edu>
Subject: Re: bin/6188: screensaver permanently active when no bounds checking for blanktime in sysinstall
Reply-To: Don Morrison <dmorrisn@u.washington.edu>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR bin/6188; it has been noted by GNATS.

From: Don Morrison <dmorrisn@u.washington.edu>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: bin/6188: screensaver permanently active when no bounds checking for blanktime in sysinstall
Date: Wed, 01 Apr 1998 03:15:46 -0800

 > > /stand/sysinstall does not make bounds checks for the screensaver
 > > time-out interval.  When this value is read from /etc/rc.conf at startup
 >
 > True enough, but considering that anyone can also change the time-out
 > value to a bogus one by typing ``vi /etc/rc.conf'' (substitute your
 > favorite editor here ;-), I think the fix doesn't belong in sysinstall
 > so much as it does in vidcontrol (which should simply refuse to set a
 > bogus timeout value, preventing its direct abuse on the command line
 > as well).
 >
 >                                         Jordan
 
 
 I'm sorry, you are correct.  It's just as easy to fix there and it actually
 fixes the problem (completely.)
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message