From owner-freebsd-current@FreeBSD.ORG  Sun Nov 23 19:43:33 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7FAAD16A4CE
	for <current@freebsd.org>; Sun, 23 Nov 2003 19:43:33 -0800 (PST)
Received: from bunrab.catwhisker.org
	(adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122])
	by mx1.FreeBSD.org (Postfix) with ESMTP id BA67043FE0
	for <current@freebsd.org>; Sun, 23 Nov 2003 19:43:32 -0800 (PST)
	(envelope-from david@catwhisker.org)
Received: from bunrab.catwhisker.org (localhost [127.0.0.1])
	hAO3hWB5002267
	for <current@freebsd.org>; Sun, 23 Nov 2003 19:43:32 -0800 (PST)
	(envelope-from david@bunrab.catwhisker.org)
Received: (from david@localhost)
	by bunrab.catwhisker.org (8.12.10/8.12.10/Submit) id hAO3hWmU002266
	for current@freebsd.org; Sun, 23 Nov 2003 19:43:32 -0800 (PST)
	(envelope-from david)
Date: Sun, 23 Nov 2003 19:43:32 -0800 (PST)
From: David Wolfskill <david@catwhisker.org>
Message-Id: <200311240343.hAO3hWmU002266@bunrab.catwhisker.org>
In-Reply-To: <20031124092346.F63116@sbk-gw.sibnet.ru>
cc: current@freebsd.org
Subject: Re: Unfortunate dynamic linking for everything
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Nov 2003 03:43:33 -0000

>Date: Mon, 24 Nov 2003 09:34:08 +0600 (NOVT)
>From: "Maxim M. Kazachek" <stranger@sberbank.sibnet.ru>

>	So, imagine, i'm accidentally deleted /bin with your most wanted
>static sh... And, of course, due to static nature of /bin/sh it was
>removed from /rescue? Nothing will protect you from shooting in the leg,
>neither static linking, nor assumption that /lib is OK.

So go ahead and make /bin/sh also have a (hard) link to /rescue/sh.
Then the referenced action merely decrements the link count, and the
executable itself doesn't go away.

Sure, you could be more imaginative with foot-shooting, but the stated
problem is really easy to avoid.

Peace,
david       (reluctant to contribute to this thread....)
-- 
David H. Wolfskill				david@catwhisker.org
If you want true virus-protection for your PC, install a non-Microsoft OS
on it.  Plausible candidates include FreeBSD, Linux, NetBSD, OpenBSD, and
Solaris (in alphabetical order).