From owner-freebsd-security Sat Jan 26 13:36: 3 2002 Delivered-To: freebsd-security@freebsd.org Received: from nic.upatras.gr (nic.upatras.gr [150.140.129.30]) by hub.freebsd.org (Postfix) with SMTP id E546C37B402 for ; Sat, 26 Jan 2002 13:35:51 -0800 (PST) Received: (qmail 14108 invoked from network); 26 Jan 2002 21:32:36 -0000 Received: from dialup3-ceid-dialinpool-9.upatras.gr (HELO hades.hell.gr) (root@150.140.128.201) by nic.upatras.gr with SMTP; 26 Jan 2002 21:32:36 -0000 Received: (from charon@localhost) by hades.hell.gr (8.11.6/8.11.6) id g0QIXjP00741; Sat, 26 Jan 2002 20:33:45 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Sat, 26 Jan 2002 20:33:45 +0200 From: Giorgos Keramidas To: Robert Simmons Cc: freebsd-security@freebsd.org Subject: Re: theo Message-ID: <20020126183344.GA659@hades.hell.gr> References: <20020125175928.H41011-100000@mail.wlcg.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: <20020125175928.H41011-100000@mail.wlcg.com> User-Agent: Mutt/1.3.25i 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 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2002-01-25 18:05:37, Robert Simmons wrote: >=20 > 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. >=20 > 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? Unless this is not available in 4-STABLE (haven't seen one around here for a while), you can always check out: $ sysctl kern.bootfile kern.bootfile: /boot/kernel/kernel Anyway. About those security alerts. The very fact that they *are* coming out, in my personal view, means that someone is actually looking into those security problems and people that develop FreeBSD don't just hide their head in the sand, and shout "NO, NO, WE ARE NOT EXPLOITABLE! WE NEVER WERE! GO AWAY NOW." Accepting the fact that problems do exist, in all software, and actually doing something about it is a Good Thing(TM), IMHO :) Cheers, --=20 Giorgos Keramidas . . . . . . . . . keramida@{ceid.upatras.gr,freebsd.org} FreeBSD Documentation Project . . . http://www.freebsd.org/docproj/ FreeBSD: The power to serve . . . . http://www.freebsd.org/ --17pEHd4RhPHOinZp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) iD8DBQE8UvaI1g+UGjGGA7YRArtKAKCDvtdEB2yy0e5jRPa/TpIvvbetOgCgkzzd zVghpYhXwpJEjAE69bKbzO0= =IrbB -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message