From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v5] fs: make dumpable=2 require fully qualified path
Date: Mon, 25 Jun 2012 15:14:09 -0700
Message-ID: <20120625151409.5e13702b.akpm@linux-foundation.org>
References: <20120625180327.GA31931@www.outflux.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: linux-kernel@vger.kernel.org, Rob Landley <rob@landley.net>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Alan Cox <alan@linux.intel.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Doug Ledford <dledford@redhat.com>,
	Serge Hallyn <serge.hallyn@canonical.com>,
	James Morris <james.l.morris@oracle.com>,
	Joe Korty <joe.korty@ccur.com>, linux-doc@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
To: Kees Cook <keescook@chromium.org>
Return-path: <linux-doc-owner@vger.kernel.org>
In-Reply-To: <20120625180327.GA31931@www.outflux.net>
Sender: linux-doc-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

On Mon, 25 Jun 2012 11:03:27 -0700
Kees Cook <keescook@chromium.org> wrote:

> Instead of introducing a suid_dumpable=3 mode and breaking all users
> of mode 2, this only disables the unsafe portion of mode 2 (writing to
> disk via relative path).

It would be nicer to generate the warning at configuration time rather than
at core-dumping time.  I have a feeling that's Hard To Do, but why?