From owner-freebsd-security Sat Dec 2 02:06:36 1995 Return-Path: owner-security Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id CAA13496 for security-outgoing; Sat, 2 Dec 1995 02:06:36 -0800 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id CAA13415 for ; Sat, 2 Dec 1995 02:06:14 -0800 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id UAA21630; Sat, 2 Dec 1995 20:37:50 GMT From: Michael Smith Message-Id: <199512022037.UAA21630@genesis.atrad.adelaide.edu.au> Subject: Re: ****HELP***** To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sat, 2 Dec 1995 20:37:49 +0000 () Cc: msmith@atrad.adelaide.edu.au, rdugaue@calweb.com, security@FreeBSD.ORG In-Reply-To: <322.817897922@time.cdrom.com> from "Jordan K. Hubbard" at Dec 2, 95 01:52:02 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 990 Sender: owner-security@FreeBSD.ORG Precedence: bulk Jordan K. Hubbard stands accused of saying: > > > Jordan; how hard would it be to generate a file with the md5's of a stock > > release system's "standard binaries" for this sort of thing? > > Probably not too hard. Let me think about it. You'd want a file > for each distrib, probably. And a script somewhere for checking it? Should we perhaps start looking at a SCO-like "perms" setup? Is this something that the security and ISP people would smile happily upon? (ie. a distribution-wide listing of md5's, permissions and ownerships, burnt onto the release CD for security's sake 8) > Jordan -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 041-122-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] "Who does BSD?" "We do Chucky, we do." [[