From: Daniel J Walsh <dwalsh@redhat.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: Eric Paris <eparis@redhat.com>,
KaiGai Kohei <kaigai@ak.jp.nec.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
James Morris <jmorris@namei.org>,
selinux@tycho.nsa.gov, Eamon Walsh <ewalsh@tycho.nsa.gov>
Subject: Re: type bounds audit messages
Date: Tue, 16 Jun 2009 11:30:56 -0400 [thread overview]
Message-ID: <4A37BAB0.100@redhat.com> (raw)
In-Reply-To: <200906161123.52932.sgrubb@redhat.com>
On 06/16/2009 11:23 AM, Steve Grubb wrote:
> On Tuesday 16 June 2009 10:55:33 am Eric Paris wrote:
>>>> I feel good for all but the { setattr write }
>>>>
>>>> It's a new message, we have no parsers which need the old format, how
>>>> would others feel about
>>>>
>>>> perm="setattr,write" ?
>>>
>>> I'd recommend losing the quotes. I think you are doing this because of
>>> untrusted_string, but I doubt the user can influence this.
>>
>> I'm starting to buy into the 'quotes makes it easy to know it's a
>> string' argument from jdennis.
>
> Any field that has a value starting and ending with quotes means that its
> encoded due to untrusted users having influence over it. That is the parsing
> rule.
>
> -Steve
>
> --
> This message was distributed to subscribers of the selinux mailing list.
> If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
> the words "unsubscribe selinux" without quotes as the message.
Well in that case you need the comma separated list.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2009-06-16 15:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1244730288.10762.120.camel@localhost.localdomain>
[not found] ` <4A31A33F.2040504@ak.jp.nec.com>
[not found] ` <1244807594.18947.62.camel@localhost.localdomain>
2009-06-15 6:56 ` type bounds audit messages KaiGai Kohei
2009-06-15 13:17 ` Eric Paris
2009-06-15 14:01 ` Stephen Smalley
2009-06-15 14:14 ` Eric Paris
2009-06-16 0:43 ` KaiGai Kohei
2009-06-16 14:26 ` Eric Paris
2009-06-16 14:40 ` Steve Grubb
2009-06-16 14:55 ` Eric Paris
2009-06-16 15:19 ` Daniel J Walsh
2009-06-16 17:18 ` Stephen Smalley
2009-06-17 13:10 ` Daniel J Walsh
2009-06-16 15:23 ` Steve Grubb
2009-06-16 15:30 ` Daniel J Walsh [this message]
2009-06-16 15:41 ` Eric Paris
2009-06-17 4:35 ` KaiGai Kohei
2009-06-17 12:53 ` Stephen Smalley
2009-06-18 8:26 ` KaiGai Kohei
2009-06-18 12:50 ` Stephen Smalley
2009-06-18 14:18 ` James Morris
2009-06-18 8:35 ` KaiGai Kohei
2009-06-18 12:54 ` Stephen Smalley
2009-06-15 14:08 ` Steve Grubb
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=4A37BAB0.100@redhat.com \
--to=dwalsh@redhat.com \
--cc=eparis@redhat.com \
--cc=ewalsh@tycho.nsa.gov \
--cc=jmorris@namei.org \
--cc=kaigai@ak.jp.nec.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=sgrubb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.