All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dave Quigley" <dquigley@gmail.com>
To: SELinux@tycho.nsa.gov
Subject: Lets try this again: Advantages and Disadvantages of Overtyping a policy
Date: Fri, 16 Feb 2007 16:08:49 -0500	[thread overview]
Message-ID: <f888952b0702161308y4a373559n581ea8a61de355ee@mail.gmail.com> (raw)

Hello,
    First I would like to apologize for the empty mail before but
gmail has a silly feature of sending a mail if you hit control +
enter. While it might be useful it has quite a few downfalls.

OK onto my actual question. I was wondering what advantages and
disadvantages there are to having too many types in a policy. I can
see if you have too many the allow rules to allow interaction within
the application itself can be excessive. However it also seems to me
that by having more types for the application you can have more
control over restriction the application. You see this in come
policies where they have separate types for their files in /var /etc
and /log however you don't see it for that many applications. I would
just like to hear people's thoughts on this.

Dave Quigley

--
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.

             reply	other threads:[~2007-02-16 21:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-16 21:08 Dave Quigley [this message]
2007-02-20 20:37 ` Lets try this again: Advantages and Disadvantages of Overtyping a policy Christopher J. PeBenito
2007-02-20 20:47   ` Stephen Smalley

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=f888952b0702161308y4a373559n581ea8a61de355ee@mail.gmail.com \
    --to=dquigley@gmail.com \
    --cc=SELinux@tycho.nsa.gov \
    /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.