From owner-freebsd-security Fri Jan 25 15: 5:46 2002 Delivered-To: freebsd-security@freebsd.org Received: from mail.wlcg.com (mail.wlcg.com [198.92.199.5]) by hub.freebsd.org (Postfix) with ESMTP id 83CB937B400 for ; Fri, 25 Jan 2002 15:05:42 -0800 (PST) Received: from mail.wlcg.com (mail.wlcg.com [198.92.199.5]) by mail.wlcg.com (8.11.6/8.11.6) with ESMTP id g0PN5f741367 for ; Fri, 25 Jan 2002 18:05:41 -0500 (EST) (envelope-from rsimmons@wlcg.com) Date: Fri, 25 Jan 2002 18:05:37 -0500 (EST) From: Robert Simmons To: freebsd-security@freebsd.org Subject: theo Message-ID: <20020125175928.H41011-100000@mail.wlcg.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Lets say someone has a machine they don't have console access to, but they know that the OS comes back every time they reboot the fucker. The kernel is on the old hard drive, with the swap garbage. The brand spanking new OS is mirrored on a twed. How can I tell that the core team's brand spanking newly de scriptkiddified kernel is the one that boots? dmesg? BTW, there isn't a floppy installed, nor a CD_ROM. Also, you win, you people get the prize for the most security alerts in one year. :) Robert Simmons Systems Administrator http://www.wlcg.com/ E3E2 C83A 95A2 DDDC BF7F 6889 74B6 5850 880E B566 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8UeTFdLZYUIgOtWYRA0WUAJwPjBg/vQtqHeICIEZq5ru3o8Y3DACgo5H1 L+E8eAkNkU9TiPxf9gsfMPc= =3yoL -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message