From owner-freebsd-chat Mon Jul 10 0: 8:57 2000 Delivered-To: freebsd-chat@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 22B1D37B76C; Mon, 10 Jul 2000 00:08:51 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id JAA73055; Mon, 10 Jul 2000 09:08:43 +0200 (CEST) (envelope-from des@flood.ping.uio.no) To: Alfred Perlstein Cc: Marius Bendiksen , Adam , chat@FreeBSD.ORG Subject: Re: making the snoop device loadable. References: <20000709165702.V25571@fw.wintelcom.net> From: Dag-Erling Smorgrav Date: 10 Jul 2000 09:08:43 +0200 In-Reply-To: Alfred Perlstein's message of "Sun, 9 Jul 2000 16:57:03 -0700" Message-ID: Lines: 18 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [moving from -arch to -chat] Alfred Perlstein writes: > * Marius Bendiksen [000709 16:54] wrote: > > Thing is; disabling kernel modules will avail you little, as an > > illegitimate user can still use the memory devices to access physical > > memory, and thus binary patch a live kernel. This is hard, but it can, and > > has been done. Eivind mentioned one particular case with a person who > > binary-patched the kernel of an old Unix to bypass the 14 character file > > name length limitation without severing the uptime. > I owe that person a beer. He's a committer (tegge@freebsd.org). The OS in question, IIRC, was DolphinOS on an ND UniLine 8820 (colloquially known as Flipper). DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message