Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 19 Nov 2001 10:08:34 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 19 Nov 2001 10:08:14 -0500 Received: from w089.z209220022.nyc-ny.dsl.cnc.net ([209.220.22.89]:34065 "HELO yucs.org") by vger.kernel.org with SMTP id ; Mon, 19 Nov 2001 10:08:10 -0500 Subject: Re: x bit for dirs: misfeature? From: Shaya Potter To: vda Cc: Alexander Viro , linux-kernel@vger.kernel.org In-Reply-To: <01111917034005.00817@nemo> In-Reply-To: <01111917034005.00817@nemo> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.99.1 (Preview Release) Date: 19 Nov 2001 10:07:30 -0500 Message-Id: <1006182451.4633.5.camel@zaphod> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2001-11-19 at 12:03, vda wrote: > On Monday 19 November 2001 14:46, Alexander Viro wrote: > > On Mon, 19 Nov 2001, vda wrote: > > > Everytime I do 'chmod -R a+rX dir' and wonder are there > > > any executables which I don't want to become world executable, > > > I think "Whatta hell with this x bit meaning 'can browse' > > > for dirs?! Who was that clever guy who invented that? Grrrr" > > > > > > Isn't r sufficient? Can we deprecate x for dirs? > > > I.e. make it a mirror of r: you set r, you see x set, > > > you clear r, you see x cleared, set/clear x = nop? > > > > See UNIX FAQ. Ability to read != ability to lookup. > > > > Trivial example: you have a directory with a bunch of subdirectories. > > You want owners of subdirectories to see them. You don't want them > > to _know_ about other subdirectories. > > Security through obscurity, that is. > > Do you have even a single dir on your boxes with r!=x? I've seen this a lot with html directories for web servers. - 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/