From owner-freebsd-security Tue Mar 27 13:23:19 2001 Delivered-To: freebsd-security@freebsd.org Received: from turtledawn.blackhelicopters.org (mag.gltg.com [198.88.118.10]) by hub.freebsd.org (Postfix) with ESMTP id 24A0837B719 for ; Tue, 27 Mar 2001 13:23:15 -0800 (PST) (envelope-from mwlucas@turtledawn.blackhelicopters.org) Received: (from mwlucas@localhost) by turtledawn.blackhelicopters.org (8.11.3/8.11.3) id f2RLNal40413 for security@freebsd.org; Tue, 27 Mar 2001 16:23:36 -0500 (EST) (envelope-from mwlucas) Date: Tue, 27 Mar 2001 16:23:35 -0500 From: Michael Lucas To: security@freebsd.org Subject: re: weird daily run output -- solved Message-ID: <20010327162335.A40356@gltg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, I'm still not sure what the problem was, but I believe it's not a security issue. I just installed a second machine, identical to the first. Lo and behold, /var/run/dmesg.boot has a bunch of the same garbage in it. Since this appeared before I plugged in the Ethernet cable, I believe I'm fairly safe in saying this isn't a security break. I want to thank you all for your help. It's probably, as one person whose name completely escapes me now suggested, the memory not clearing entirely on shutdown. Sigh. If only boxes came with a big red light that said "YOU HAVE BEEN 0WN3D". ==ml -- Michael Lucas | for assistance, email Internal Support | support@gltg.com or call Great Lakes Technologies Group | 248-204-7256 mlucas@gltg.com, 248-204-7258 | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message