Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759499AbXIZLfI (ORCPT ); Wed, 26 Sep 2007 07:35:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758487AbXIZLe4 (ORCPT ); Wed, 26 Sep 2007 07:34:56 -0400 Received: from h90-m1.hosting90.cz ([81.0.225.70]:52282 "EHLO h90-m1.hosting90.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753960AbXIZLez (ORCPT ); Wed, 26 Sep 2007 07:34:55 -0400 Message-ID: <46FA43DD.7090703@prepere.com> Date: Wed, 26 Sep 2007 13:34:53 +0200 From: Miloslav Semler User-Agent: IceDove 1.5.0.12 (X11/20070607) MIME-Version: 1.0 To: Alan Cox CC: linux-kernel@vger.kernel.org Subject: Re: Chroot bug References: <56705.193.171.152.61.1190289559.squirrel@webmail.marek.priv.at> <46F29A9A.4070806@davidnewall.com> <200709201817.17282@x5> <46F2B59F.8090709@davidnewall.com> <46F2DDD0.3030500@tmr.com> <46F380E4.4040606@davidnewall.com> <20070924213215.GA32716@vino.hallyn.com> <46F83474.5040503@davidnewall.com> <20070924230008.GA3160@vino.hallyn.com> <46F8BC8A.7080006@davidnewall.com> <20070925114947.GA9721@vino.hallyn.com> <46F91417.9050600@davidnewall.com> <46F924E3.50205@davidnewall.com> <20070925163040.12a3c2f8@the-village.bc.nu> <46F92AAB.1060903@davidnewall.com> <20070925164806.4cadc6a5@the-village.bc.nu> <46F99EDE.70905@davidnewall.com> <20070926011847.49bbb9a2@the-village.bc.nu> <46FA334F.7030802@davidnewall.com> <20070926114729.3b9d1fb4@the-village.bc.nu> <46FA3D4B.20805@davidnewall.com> <20070926122028.5f842d1e@the-village.bc.nu> <46FA41B4.9040104@prepere.com> <20070926123522.54ffd56f@the-village.bc.nu> In-Reply-To: <20070926123522.54ffd56f@the-village.bc.nu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 778 Lines: 18 Alan Cox napsal(a): >> but many program use this as security feature. So do you think that bind >> may use vserver? >> > > It would be a lot stronger if it did. A bind running non-root will be > probably safe. A bind running as root can be attacked and break out of a > chroot trivially. I guess it depends how you run bind. > but not bind with selinux. It can chroot, but not does other things. So there is an question: Why we do not fix it. Tell me please some other reason than "you can workaround chroot other ways". - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/