All of lore.kernel.org
 help / color / mirror / Atom feed
From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] I think we made a large mistake when we designed apache_content_template.
Date: Wed, 23 Oct 2013 15:40:52 -0400	[thread overview]
Message-ID: <52682644.3050705@redhat.com> (raw)
In-Reply-To: <1382556579.3041.114.camel@d30>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/23/2013 03:29 PM, Dominick Grift wrote:
> On Wed, 2013-10-23 at 21:14 +0200, Sven Vermeulen wrote:
> 
>> 
>> But another thought: isn't it sufficient to base logic on attributes
>> here?
> 
> Boolean identifiers are just as configurable as any other identifiers
> 
> The only thing you can rely on is access vectors, and keywords
> 
> You cannot do as much with those as you could, in theory, with the addition
> of identifiers
> 
>> _______________________________________________ refpolicy mailing list 
>> refpolicy at oss.tresys.com 
>> http://oss.tresys.com/mailman/listinfo/refpolicy
> 
> 
Yes I think we could attempt to do all of these things, and I agree that it is
somwhat flimsy, but it is the best we have right now.

In Fedora right now we have

seinfo -t | awk '{ print $1 }'| grep ^http | wc -l
183

One potential idea would be to have the tooling create an attribute based on
the module name (Not good for non Modular policy).  Then we could assign the
attribute to all types defined within the module.

httpd_module_attribue for example.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlJoJkQACgkQrlYvE4MpobOhJwCbB5SQp0FncpZFkffvKlikh6jn
zqQAnRFWEZmRRhCyFmHO2AGpN8czOWPs
=YJx1
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2013-10-23 19:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-23 17:57 [refpolicy] I think we made a large mistake when we designed apache_content_template Daniel J Walsh
2013-10-23 19:13 ` Dominick Grift
2013-10-23 19:14 ` Sven Vermeulen
2013-10-23 19:29   ` Dominick Grift
2013-10-23 19:30     ` Dominick Grift
2013-10-23 19:40     ` Daniel J Walsh [this message]
2013-10-23 19:38 ` Dominick Grift
2013-10-23 19:44   ` Daniel J Walsh
2013-10-23 20:22     ` Dominick Grift

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=52682644.3050705@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=refpolicy@oss.tresys.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.