From owner-freebsd-current  Sun Sep 24 15:07:40 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id PAA17145
          for current-outgoing; Sun, 24 Sep 1995 15:07:40 -0700
Received: from mramirez.sy.yale.edu (mramirez.sy.yale.edu [130.132.57.207])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA17134
          for <freebsd-current@freefall.freebsd.org>; Sun, 24 Sep 1995 15:07:36 -0700
Received: (from mrami@localhost) by mramirez.sy.yale.edu (8.6.12/8.6.9) id SAA03448; Sun, 24 Sep 1995 18:07:33 -0400
Date: Sun, 24 Sep 1995 18:07:33 -0400 (EDT)
From: Marc Ramirez <mrami@mramirez.sy.yale.edu>
Reply-To: mrami@minerva.cis.yale.edu
To: James Leppek <jleppek@suw2k.ess.harris.com>
cc: freebsd-current@freefall.freebsd.org
Subject: Re: runtime warnings
In-Reply-To: <9509232113.AA07376@borg.ess.harris.com>
Message-ID: <Pine.BSF.3.91.950924180625.1770C-100000@mramirez.sy.yale.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@FreeBSD.org
Precedence: bulk

On Sat, 23 Sep 1995, James Leppek wrote:

> This may have come up before but what is the purpose of
> having runtime warnings for things like gets. Compile time warnings
> I can understand, but runtime??? I give someone the latest gnuchess
> and everytime they start it, up pops this warning about gets being
> unsafe. To most folks that means "don't run this program, it's broken".

As a local security guy, I would agree with "most folks'" assessment 
there. :)

Marc.