From: Steve Grubb <sgrubb@redhat.com>
To: Eric Paris <eparis@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: PATH records show fcaps
Date: Mon, 20 Oct 2008 22:21:06 -0400 [thread overview]
Message-ID: <200810202221.06482.sgrubb@redhat.com> (raw)
In-Reply-To: <1224543619.3189.193.camel@paris-laptop>
On Monday 20 October 2008 19:00:19 Eric Paris wrote:
> so choices
>
> 1) cap_fP, cap_fE, cap_fI
> 2) cap_fp, cap_fe, cap_fi
> 3) capprm_file, capeff_file, capinh_file
>
> If steve feels strongly about not going down #1 (which obviously I
> liked!) I vote #2.....
Yes, #2 is fine.
Thanks,
-Steve
next prev parent reply other threads:[~2008-10-21 2:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-18 15:23 PATH records show fcaps Eric Paris
2008-10-20 10:56 ` Steve Grubb
2008-10-20 13:32 ` Eric Paris
2008-10-20 16:31 ` Serge E. Hallyn
2008-10-20 16:55 ` Eric Paris
2008-10-20 17:13 ` Serge E. Hallyn
2008-10-20 22:52 ` Steve Grubb
2008-10-20 23:00 ` Eric Paris
2008-10-21 2:21 ` Steve Grubb [this message]
2008-10-20 16:33 ` Serge E. Hallyn
2008-10-20 17:55 ` Eric Paris
2008-10-20 18:13 ` Serge E. Hallyn
2008-10-20 18:35 ` Eric Paris
2008-10-20 19:13 ` Serge E. Hallyn
2008-10-20 19:49 ` Eric Paris
2008-10-20 20:01 ` Serge E. Hallyn
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=200810202221.06482.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=eparis@redhat.com \
--cc=linux-audit@redhat.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