From owner-freebsd-bugs  Wed Apr  1 03:52:11 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id DAA11828
          for freebsd-bugs-outgoing; Wed, 1 Apr 1998 03:52:11 -0800 (PST)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA11785
          for <freebsd-bugs@hub.freebsd.org>; Wed, 1 Apr 1998 03:52:06 -0800 (PST)
          (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp)
Received: by outmail.utsunomiya-u.ac.jp id AA15663; Wed, 1 Apr 1998 20:52:00 +0900
Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP
	id VAA07908; Wed, 1 Apr 1998 21:00:26 +0900 (JST)
Message-Id: <199804011200.VAA07908@zodiac.mech.utsunomiya-u.ac.jp>
To: Don Morrison <dmorrisn@u.washington.edu>
Cc: freebsd-bugs@hub.freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: bin/6188: screensaver permanently active when no bounds checking
	 for blanktime in sysinstall 
In-Reply-To: Your message of "Wed, 01 Apr 1998 03:20:02 PST."
             <199804011120.DAA06730@hub.freebsd.org> 
References: <199804011120.DAA06730@hub.freebsd.org> 
Date: Wed, 01 Apr 1998 21:00:25 +0900
From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>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.)

Even better, more fundamental fix is to fix syscons :-)

Perhaps, something like 24 hours (24*60*60 = 86400 secs) is the
reasonable maximum value allowed?

Kazu

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