Date: Sat, 2 Dec 1995 13:14:42 -0500 (EST) From: Robert Watson <robert@fledge.watson.org> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: Michael Smith <msmith@atrad.adelaide.edu.au>, Robert Du Gaue <rdugaue@calweb.com>, security@FreeBSD.ORG Subject: Re: ****HELP***** Message-ID: <Pine.BSF.3.91.951202131254.17800D-100000@fledge.watson.org> In-Reply-To: <322.817897922@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Actually, what might be nice is to include the MD5's with the system, and have a script in daily.local that verifies that the key system binaries are correct. Obviously then the md5 file would be at risk, but.. This would also be nice, unrelated to the daily part, after an upgrade to check if there are any old binaries lying around. Actually, one thing I was going to ask about was -- is there a difference between the 2.1.0 binaries for standard executables (eg., pine) and the 2.0.5 ones? Is there anyway I can use strings (or something) to get a list of all the old binaries on my system and upgrade them if needed? On Sat, 2 Dec 1995, Jordan K. Hubbard wrote: > > 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. > > Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.951202131254.17800D-100000>