Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932153Ab1FVKRb (ORCPT ); Wed, 22 Jun 2011 06:17:31 -0400 Received: from mail-bw0-f46.google.com ([209.85.214.46]:34243 "EHLO mail-bw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752707Ab1FVKRa (ORCPT ); Wed, 22 Jun 2011 06:17:30 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=nz20qGZz01Y7JbW6ibdXgD8O0661ywUHU8L4RAp+/CCB7VkMt+NyH8oL2swcywSaei 6kdcaNpP5IAcJ4cq5Dm2fyAHJSIcNaUGcQBLOzTZ2nDEKgVGmETHrmAJbuxwd/YJHSKc F2btuxBqh4GTpupyM9h3EZzeAPgrvcTKT25fU= Date: Wed, 22 Jun 2011 14:17:24 +0400 From: Vasiliy Kulikov To: Andrew Morton Cc: linux-kernel@vger.kernel.org, kernel-hardening@lists.openwall.com, Greg Kroah-Hartman , "David S. Miller" , Arnd Bergmann , Alexey Dobriyan , linux-security-module@vger.kernel.org Subject: Re: [RFC 0/5 v4] procfs: introduce hidepid=, hidenet=, gid= mount options Message-ID: <20110622101724.GA4278@albatros> References: <1308163895-5963-1-git-send-email-segoon@openwall.com> <20110621153102.762557f3.akpm@linux-foundation.org> <20110622064545.GA3605@albatros> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110622064545.GA3605@albatros> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1195 Lines: 33 On Wed, Jun 22, 2011 at 10:45 +0400, Vasiliy Kulikov wrote: > More generic solution (I'm not suggesting it, but merely discussing) > would use some user-supplied set of files to restrict access to (or, > better, the set of allowed files because white list is almost always > better than black list). Maybe this one: > > mount -t proc -o "pid_allow=exe,status,comm,oom_*" proc /proc > > And without pid_allow it would behave like pid_allow=*. > "pid_allow=." > would deny access to the whole /proc/PID. I mean "pid_allow=", of course. > This would be a bit inconsistent with current permissions because e.g. > if use pid_allow=environ then environ file would not be accessible > because of posix permissions. Hierarchical mode (pid_allow=fd/1) is not > allowed too. For hierarchical mode: attr_allowed, tgid_allowed, tid_allowed. Thanks, -- Vasiliy Kulikov http://www.openwall.com - bringing security into open computing environments -- 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/