From: Pavel Machek Subject: Re: symlinks with permissions Date: Wed, 28 Oct 2009 22:06:24 +0100 Message-ID: <20091028210623.GB4159@elf.ucw.cz> References: <20091025062953.GC1391@ucw.cz> <20091026163157.GB7233@duck.suse.cz> <20091026165729.GF23564@us.ibm.com> <20091026173629.GB16861@fieldses.org> <20091026174631.GD7233@duck.suse.cz> <1256579869.8576.7.camel@heimdal.trondhjem.org> <20091025093604.GA1501@ucw.cz> <20091028081653.GA18290@elf.ucw.cz> <4AE87292.20802@schaufler-ca.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Eric W. Biederman" , Trond Myklebust , Jan Kara , "J. Bruce Fields" , "Serge E. Hallyn" , kernel list , linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk, jamie@shareable.org To: Casey Schaufler Return-path: Content-Disposition: inline In-Reply-To: <4AE87292.20802@schaufler-ca.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org > > Please see bugtraq discussion at > > http://seclists.org/bugtraq/2009/Oct/179 . > > > > (In short, you get read-only fd, and you can upgrade it to read-write > > fd. Yes, you are the owner of the process, but you are not owner of > > the file the fd refers to.) > > > > The actual permissions of the file are not ignored, but permissions of > > the containing directory _are_. If there's 666 file in 700 directory, > > you can reopen it read-write, in violation of directory's 700 > > permissions. > > There is no security violation here. Consider the case where You are able to write to my files, when unix permissions forbid that. How do you call that? Strange behaviour of /proc/*/fd/ symlink that is not really a symlink allows that. See bugtraq discussion at http://seclists.org/bugtraq/2009/Oct/179 . Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html