mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave McCracken <dmccr@us.ibm.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, Bill Abt <babt@us.ibm.com>
Subject: Re: [PATCH 2.5.30] Allow tasks to share credentials
Date: Fri, 02 Aug 2002 16:12:53 -0500	[thread overview]
Message-ID: <111710000.1028322773@baldur.austin.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0208021016580.914-100000@home.transmeta.com>


--On Friday, August 02, 2002 10:22:54 AM -0700 Linus Torvalds
<torvalds@transmeta.com> wrote:

> But I _know_, for example, that this is just a horrid security hole the
> way it is now - the execve() path doesn't create a unique "cred"
> structure, so if you execve() a suid binary from a CLONE_CRED thread, the
> other threads get the suid'ness and can do whatever they want.

You are entirely correct.  It was an oversight on my part.  execve() should
always unshare the cred structure.  I'll work up a fixed version.

Dave McCracken

======================================================================
Dave McCracken          IBM Linux Base Kernel Team      1-512-838-3059
dmccr@us.ibm.com                                        T/L   678-3059


  reply	other threads:[~2002-08-02 21:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <44230000.1028304881@baldur.austin.ibm.com>
2002-08-02 17:22 ` Linus Torvalds
2002-08-02 21:12   ` Dave McCracken [this message]
     [not found] <200208022006.g72K6ctD012092@baldur.austin.ibm.com>
2002-08-02 20:10 ` Linus Torvalds
2002-08-02 20:31   ` Dave McCracken

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=111710000.1028322773@baldur.austin.ibm.com \
    --to=dmccr@us.ibm.com \
    --cc=babt@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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

all inboxes | Powered by JetHome®