All of lore.kernel.org
 help / color / mirror / Atom feed
From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Help with policy writing
Date: Wed, 29 Oct 2008 08:37:52 -0400	[thread overview]
Message-ID: <49085920.30501@redhat.com> (raw)
In-Reply-To: <af1a12460810261143t340d51bwad304430a5607451@mail.gmail.com>

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


/usr/local/sbin/samhain --
gen_context(system_u:object_r:samhain_exec_t,s0)

DAN> I would make this more generic maybe make the local optional

/usr/(local/)?sbin/samhain --
gen_context(system_u:object_r:samhain_exec_t,s0)


/etc/samhainrc  --      gen_context(system_u:object_r:samhain_config_t,s0)


/var/run/samhain.pid    --
gen_context(system_u:object_r:samhain_pid_t,s0)
/var/run/samhain_log.lock
gen_context(system_u:object_r:samhain_lock_t,s0)

I think these should be treated the same and labeled samhain_var_run_t

Unless there are different security properties between the pid file and
the lock file, no reason to label them differently.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkkIWR8ACgkQrlYvE4MpobP0OQCeNtwQ9LuZ8IpLMFerpJH9HjAq
V2gAoJOT3Gu+ZPLvkBaEWyMYoJ96O8uo
=zb5o
-----END PGP SIGNATURE-----

      parent reply	other threads:[~2008-10-29 12:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-26 18:43 [refpolicy] Help with policy writing Konrad Azzopardi
2008-10-26 18:58 ` Dominick Grift
2008-10-27 13:22   ` Brandon Whalen
2008-10-27 15:30     ` Konrad Azzopardi
2008-10-29 12:37 ` Daniel J Walsh [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=49085920.30501@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.