From owner-freebsd-questions Sat Feb 8 17:59:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA15151 for questions-outgoing; Sat, 8 Feb 1997 17:59:13 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA15140 for ; Sat, 8 Feb 1997 17:59:09 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id SAA05603; Sat, 8 Feb 1997 18:00:10 -0800 (PST) Message-Id: <199702090200.SAA05603@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: bill@twwells.com (T. William Wells) cc: freebsd-questions@freebsd.org Subject: Re: 2.1.7 binaries and 2.1.5 system (fwd) In-reply-to: Your message of "Sat, 08 Feb 1997 20:16:42 EST." From: David Greenman Reply-To: dg@root.com Date: Sat, 08 Feb 1997 18:00:10 -0800 Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> I want to do a quick substitution of the 2.1.7 setuid programs >> (when 2.1.7 comes out) into my 2.1.5 system, as I don't have the >> time to do a full upgrade. Any caveats? > >Oh, and before anyone else tells me -- yes, I know what I'm doing, >e.g., libc has to be replaced or I have to statically link those >setuid programs. And I have to trace down program calls to ensure >that the bugs don't get invoked in unreplaced programs. > >I'm concerned about kernel call changes, file format changes, and >the like -- stuff that I'd have to spend hours reading the source >to find. If I were going to do that, I'd just go ahead and do a >full upgrade! There are no incompatibilites like this that I know of. You should have no trouble with a mix of 2.1.5, 2.1.6, and 2.1.7 executables...although you _should_ upgrade all of system binaries to 2.1.7 as there will be many other potential security holes fixed in the release, too. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project