public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Subrata Modak <subrata@linux.vnet.ibm.com>
Cc: Casey Schaufler <casey@schaufler-ca.com>,
	ltp-list <ltp-list@lists.sf.net>,
	James Morris <jmorris@namei.org>
Subject: Re: [LTP] [Testing 2.6.31] Don't raise all privs on setuid-root file	with fE set
Date: Sun, 13 Sep 2009 15:05:54 -0500	[thread overview]
Message-ID: <20090913200554.GA21695@us.ibm.com> (raw)
In-Reply-To: <1252847779.5357.31.camel@subratamodak.linux.ibm.com>

Quoting Subrata Modak (subrata@linux.vnet.ibm.com):
> Hi Serge,
> 
> Is there any requirement to adjust LTP Filecaps tests against the
> backdrop of Filecaps changes in 2.6.31 kernel, documented here:
> 
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=b5f22a59c0356655a501190959db9f7f5dd07e3f,
> 
> Regards--
> Subrata

No, coexistence of suid-root and file capabilities are not currently
tested.

-serge

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      reply	other threads:[~2009-09-13 20:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-13 13:16 [LTP] [Testing 2.6.31] Don't raise all privs on setuid-root file with fE set Subrata Modak
2009-09-13 20:05 ` Serge E. Hallyn [this message]

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=20090913200554.GA21695@us.ibm.com \
    --to=serue@us.ibm.com \
    --cc=casey@schaufler-ca.com \
    --cc=jmorris@namei.org \
    --cc=ltp-list@lists.sf.net \
    --cc=subrata@linux.vnet.ibm.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