From owner-freebsd-security  Tue Mar 27 12:58:46 2001
Delivered-To: freebsd-security@freebsd.org
Received: from moek.pir.net (moek.pir.net [130.64.1.215])
	by hub.freebsd.org (Postfix) with ESMTP id 3FD9A37B71A
	for <freebsd-security@freebsd.org>; Tue, 27 Mar 2001 12:58:44 -0800 (PST)
	(envelope-from pir@pir.net)
Received: from pir by moek.pir.net with local (Exim)
	id 14i0Y6-0003nC-00
	for freebsd-security@freebsd.org; Tue, 27 Mar 2001 15:58:42 -0500
Date: Tue, 27 Mar 2001 15:58:42 -0500
From: Peter Radcliffe <pir@pir.net>
To: freebsd-security@freebsd.org
Subject: Re: weird daily check output
Message-ID: <20010327155842.C12888@pir.net>
Reply-To: freebsd-security@freebsd.org
Mail-Followup-To: freebsd-security@freebsd.org
References: <99q631$2htl$1@FreeBSD.csie.NCTU.edu.tw> <00af01c0b6fe$79176a60$db9497cf@singingtree.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <00af01c0b6fe$79176a60$db9497cf@singingtree.com>; from mikey@singingtree.com on Tue, Mar 27, 2001 at 12:42:41PM -0800
X-fish: <darwin><
X-Copy-On-Listmail: Please do NOT Cc: me on list mail.
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

"Michael A. Dickerson" <mikey@singingtree.com> probably said:
> scans.  Then the binary garbage at the top of the dmesg has the look of a
> buffer overflow, although I don't have any explanation for how it could wind
> up in kernel memory.

binary garbage like that before and between dmesg info is pretty
common on machines that do not clear that section of memory on a
reboot (like my vaio laptop doesn't).

If you look at the dmesg infor theres a reboot message part way
through.

P.

-- 
pir                  pir@pir.net                    pir@net.tufts.edu


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