From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753500AbbAKBRT (ORCPT ); Sat, 10 Jan 2015 20:17:19 -0500 Received: from 216-12-86-13.cv.mvl.ntelos.net ([216.12.86.13]:36462 "EHLO brightrain.aerifal.cx" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750866AbbAKBRQ (ORCPT ); Sat, 10 Jan 2015 20:17:16 -0500 Date: Sat, 10 Jan 2015 20:15:59 -0500 From: Rich Felker To: "Eric W. Biederman" Cc: Al Viro , David Drysdale , "Michael Kerrisk (man-pages)" , Andy Lutomirski , Meredydd Luff , "linux-kernel@vger.kernel.org" , Andrew Morton , David Miller , Thomas Gleixner , Stephen Rothwell , Oleg Nesterov , Ingo Molnar , "H. Peter Anvin" , Kees Cook , Arnd Bergmann , Christoph Hellwig , X86 ML , linux-arch , Linux API , sparclinux@vger.kernel.org Subject: Re: [PATCHv10 man-pages 5/5] execveat.2: initial man page for execveat(2) Message-ID: <20150111011559.GG4574@brightrain.aerifal.cx> References: <20150109223300.GO22149@ZenIV.linux.org.uk> <20150109224252.GY4574@brightrain.aerifal.cx> <20150109225743.GP22149@ZenIV.linux.org.uk> <20150109231248.GZ4574@brightrain.aerifal.cx> <20150109233644.GR22149@ZenIV.linux.org.uk> <20150110030300.GU22149@ZenIV.linux.org.uk> <20150110034144.GC4574@brightrain.aerifal.cx> <20150110041457.GV22149@ZenIV.linux.org.uk> <20150110055713.GE4574@brightrain.aerifal.cx> <878uhaqnjo.fsf@x220.int.ebiederm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <878uhaqnjo.fsf@x220.int.ebiederm.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jan 10, 2015 at 04:27:23PM -0600, Eric W. Biederman wrote: > Rich Felker writes: > > > On Sat, Jan 10, 2015 at 04:14:57AM +0000, Al Viro wrote: > > >> Except that if your interpreter does stat(2) (or access(2), or getxattr(2), > >> etc.) before bothering with open(2), you'll get screwed. > > > > Yes, but I think that would be very bad interpreter design. > > stat/getxattr/access/whatever followed by open is always a TOCTOU > > race. The correct sequence of actions is always open followed by > > fstat/fgetxattr/... > > Sigh. I think everyone who has looked at this has been blind. > > If userspace is reasonable all we have to do is fix /proc/self/exe > for shell scripts to point at the actual script, > and then pass /proc/self/exe on the shell scripts command line. > > At a practical level we have to worry about backwards compability and > chroot jails. But the existence of a clean implementation with > /proc/self/exe serves a proof of concept that it would not be too > difficult. When someone cares enough to implement it. Is /proc/self/exe a "magic symlink" that's bound to the inode, or just a regular symlink? In the latter case it defeats the whole purpose of using O_EXEC fds and fexecve rather than pathnames. Rich