public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Athanasius <link@miggy.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Cc: Athanasius <link@miggy.org>, Julien TINNES <jt@cr0.org>,
	Greg KH <gregkh@suse.de>, Tavis Ormandy <taviso@sdf.lonestar.org>,
	Christoph Hellwig <hch@infradead.org>,
	Kees Cook <kees@ubuntu.com>, Eugene Teo <eugene@redhat.com>
Subject: Re: [link@miggy.org: Re: [patch 2/8] personality: fix PER_CLEAR_ON_SETID (CVE-2009-1895)]
Date: Sun, 19 Jul 2009 20:39:17 +0100	[thread overview]
Message-ID: <20090719193917.GK6722@miggy.org> (raw)
In-Reply-To: <alpine.LFD.2.01.0907191219230.13838@localhost.localdomain>

On Sun, Jul 19, 2009 at 12:27:05PM -0700, Linus Torvalds wrote:
> On Sun, 19 Jul 2009, Athanasius wrote:
> > 
> >   And it's that "as long as we ..." that still bothers me.  I've *never*
> > had any need for any use of this personality feature and this net/tun.c
> > exploit has proven there can be security gotchas with it.
> 
> I do agree. Some of those features may not be worth the cost.
> 
...
> 
> So I do agree that we can probably get rid of some really dated 
> personality bits. But I don't think we can really get rid of the concept. 
> Because compatibility is always of paramount importance.

  Would you agree that having these features default-off would be best?
That way a user or sysadmin isn't suddenly surprised by different
behaviour.  And those users who do need the functionality can turn it
on.  Whether that be via compile-time option or a sysctl I leave up to
the people who know more about Linux Kernel coding than I.  However, I'd
guess in the interests of vendor-kernel flexibility it should tend
towards the latter.
  And, of course, this is what I *thought* Execution Domains were for
when looking at the code.  Have only the default one and you're limited
pretty much to 'vanilla Linux'.  Actually have available a module for
another personality and you allow its selection by users.

  Put the choice in the hands of all users (read sysadmins even if its
their personal machine) rather than only in the hands of those who can
be bothered to recompile the kernel with an option, and currently
needing to hand-edit the source themselves to change the behaviour.

-- 
- Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/
                  Finger athan(at)fysh.org for PGP key
	   "And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence." Paula Cole - ME

  reply	other threads:[~2009-07-19 19:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090718202512.GA19587@suse.de>
     [not found] ` <alpine.LFD.2.01.0907181342500.13838@localhost.localdomain>
2009-07-18 21:28   ` [link@miggy.org: Re: [patch 2/8] personality: fix PER_CLEAR_ON_SETID (CVE-2009-1895)] Athanasius
2009-07-19  1:38     ` Julien TINNES
2009-07-19 12:27       ` Athanasius
2009-07-19 19:27         ` Linus Torvalds
2009-07-19 19:39           ` Athanasius [this message]
2009-07-19 19:47             ` Linus Torvalds
2009-07-19 19:55           ` Andi Kleen
2009-07-19 22:01           ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090719193917.GK6722@miggy.org \
    --to=link@miggy.org \
    --cc=eugene@redhat.com \
    --cc=gregkh@suse.de \
    --cc=hch@infradead.org \
    --cc=jt@cr0.org \
    --cc=kees@ubuntu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=taviso@sdf.lonestar.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox