mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Chase Venters <chase.venters@clientec.com>
Cc: Greg KH <gregkh@suse.de>, Andrew Morton <akpm@osdl.org>,
	torvalds@osdl.org, linux-kernel@vger.kernel.org,
	stable@kernel.org
Subject: Re: [stable] Re: Linux 2.6.17.4
Date: Thu, 6 Jul 2006 16:54:07 -0700	[thread overview]
Message-ID: <20060706235407.GB13418@kroah.com> (raw)
In-Reply-To: <200607061824.46990.chase.venters@clientec.com>

On Thu, Jul 06, 2006 at 06:24:23PM -0500, Chase Venters wrote:
> On Thursday 06 July 2006 17:28, Greg KH wrote:
> >  		case PR_SET_DUMPABLE:
> > -			if (arg2 < 0 || arg2 > 2) {
> > +			if (arg2 < 0 || arg2 > 1) {
> >  				error = -EINVAL;
> >  				break;
> >  			}
> 
> Am I staring at this crooked, or not looking deep enough? My manual page for 
> prctl says 2 is valid there. Specifically:
> 
>               Since  kernel 2.6.13, the value 2 is also permitted; this causes
>               any binary which normally would not be dumped to be dumped read-
>               able   by   root   only.    (See   also   the   description   of
>               /proc/sys/fs/suid_dumpable in proc(5).)
> 
> ...has something changed, and my manpages don't reflect it? Did I miss a 
> conversation about this?

Please refer to the CVE number for details.

thanks,

greg k-h

  reply	other threads:[~2006-07-06 23:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-06 22:27 Greg KH
2006-07-06 22:28 ` Greg KH
2006-07-06 22:43   ` Scott J. Harmon
2006-07-06 22:46     ` Greg KH
2006-07-06 22:54       ` Scott J. Harmon
2006-07-07  6:12         ` Jan Engelhardt
2006-07-06 23:49       ` Willy Tarreau
2006-07-06 23:53         ` [stable] " Greg KH
2006-07-06 23:56         ` Chris Wright
2006-07-06 23:57         ` Chase Venters
2006-07-06 23:24   ` Chase Venters
2006-07-06 23:54     ` Greg KH [this message]
2006-07-07 10:34     ` Marcel Holtmann

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=20060706235407.GB13418@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=chase.venters@clientec.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=torvalds@osdl.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
all inboxes | Powered by JetHome®