From owner-freebsd-current  Tue Dec 23 17:10:46 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id RAA27215
          for current-outgoing; Tue, 23 Dec 1997 17:10:46 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA27208
          for <current@freebsd.org>; Tue, 23 Dec 1997 17:10:38 -0800 (PST)
          (envelope-from imp@village.org)
Received: from harmony [10.0.0.6] 
	by rover.village.org with esmtp (Exim 1.71 #1)
	id 0xkfLI-0004px-00; Tue, 23 Dec 1997 18:10:36 -0700
Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id SAA26051 for <current@freebsd.org>; Tue, 23 Dec 1997 18:10:44 -0700 (MST)
Message-Id: <199712240110.SAA26051@harmony.village.org>
To: current@freebsd.org
Subject: Checkins
Date: Tue, 23 Dec 1997 18:10:44 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I'm finishing the checking that I started a long time ago that added
sanity checking to the size of the return value for gethostbyaddr.
Likely not strictly necessary, but will guard against possible bugs in
the bind implementation related to hosts that return too much
information.  When I committed the first of these changes, I asked for
opinions about this, and got none.  I've been running these in my tree
for the past 6 months w/o a hitch.

I doubt they need to be merged into -stable.  There isn't a way, as
far as i know, to exploit them.  If others disagree, please let me
know.

Warner