From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH v3 0/3] Introduce mutt policy
Date: Sun, 13 Nov 2011 10:20:44 +0100 [thread overview]
Message-ID: <20111113092044.GA577@siphos.be> (raw)
Please find in the following e-mails an initial policy for the mutt
application (terminal e-mail client). The set of mails contains:
- the mutt definition (.te, .if, .fc)
- adding mutt_role to unprivuser and staff
- update gpg.te to grant it rw access to mutt's tmp files
With respect to the previous (v2) patchset, this has coding style fixes,
using userdom_user_tmp_file and removes a test rule that was forgotten
earlier.
Wkr,
Sven Vermeulen
next reply other threads:[~2011-11-13 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 9:20 Sven Vermeulen [this message]
2011-11-13 9:21 ` [refpolicy] [PATCH v3 1/3] Initial policy for the mutt e-mail client Sven Vermeulen
2011-11-13 9:22 ` [refpolicy] [PATCH v3 2/3] Allow gpg to read/write mutt e-mail files (for signing) Sven Vermeulen
2011-11-13 9:23 ` [refpolicy] [PATCH v3 3/3] Allow users and staff to use mutt Sven Vermeulen
-- strict thread matches above, loose matches on Subject: below --
2011-10-28 18:01 [refpolicy] [PATCH v3 0/3] Introduce mutt policy Sven Vermeulen
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=20111113092044.GA577@siphos.be \
--to=sven.vermeulen@siphos.be \
--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.