From: guido@trentalancia.com (Guido Trentalancia)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH/RFC 0/19]: patch set to update the git reference policy
Date: Mon, 24 Jan 2011 01:43:40 +0100 [thread overview]
Message-ID: <1295829820.3862.59.camel@tesla.lan> (raw)
In-Reply-To: <4D397E26.4090904@tresys.com>
Hello again !
I am resubmitting the changes that I proposed a few days ago for the
latest reference policy. There are a few additions and now the patch has
been split into a set of 19 logical patches.
However, there might be unavoidable dependencies between a few patches.
I have applied the patches in the following order (and I cannot
guarantee that they can still be applied in a different order,
especially because of the above mentioned dependencies, e.g. on new
interfaces):
1/19: refpolicy-git-18012011-update-file-contexts.patch
2/19: refpolicy-git-18012011-update-dbus-messaging.patch
3/19: refpolicy-git-18012011-update-readahead.patch
4/19: refpolicy-git-18012011-update-cpufreqselector.patch
5/19: refpolicy-git-18012011-update-mount.patch
6/19: refpolicy-git-18012011-update-kernel-new-interfaces.patch
7/19: refpolicy-git-18012011-update-sysadm-role.patch
8/19: refpolicy-git-18012011-update-dbus.patch
9/19: refpolicy-git-18012011-update-devicekit.patch
10/19: refpolicy-git-18012011-update-networkmanager.patch
11/19: refpolicy-git-18012011-update-setroubleshoot.patch
12/19: refpolicy-git-18012011-update-smartmon.patch
13/19: refpolicy-git-18012011-update-authlogin.patch
14/19: refpolicy-git-18012011-update-logging.patch
15/19: refpolicy-git-18012011-update-selinuxutil.patch
16/19: refpolicy-git-18012011-update-sysnetwork-new-interface.patch
17/19: refpolicy-git-18012011-update-sysnetwork-hal-read-pid-files.patch
18/19: refpolicy-git-18012011-update-consolekit.patch
19/19: refpolicy-git-18012011-update-plymouth.patch
In general, this is a starting point, because I could not test all
available modules, but in the future I might submit other patches for
other modules.
I have only tested the resulting policy with the following build
configuration:
TYPE=mcs DISTRO=redhat MONOLITHIC=n UBAC=n
however I don't expect many issues with other kinds of builds.
As already explained, the patch set aims to update some permissions
needed on a modern generic Linux system. I have not used any specific
distribution and all packages are in general latest upstream versions.
Thanks very much for your attention and for your time. The patch set
follows in separate messages to the Reference Policy mailing list having
the subject "[PATCH/RFC x/19]: patch set to update the git reference
policy", with the integer x varying from 1 to 19.
Regards,
Guido Trentalancia
next prev parent reply other threads:[~2011-01-24 0:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 0:40 [refpolicy] RFC: patch to update git reference policy Guido Trentalancia
2011-01-20 13:18 ` Christopher J. PeBenito
2011-01-20 17:32 ` Guido Trentalancia
2011-01-21 12:37 ` Christopher J. PeBenito
2011-01-24 0:43 ` Guido Trentalancia [this message]
2011-01-24 15:01 ` [refpolicy] [PATCH/RFC 0/19]: patch set to update the " Dominick Grift
2011-01-24 15:56 ` Guido Trentalancia
2011-01-24 15:59 ` Dominick Grift
2011-01-24 21:01 ` Guido Trentalancia
2011-01-24 21:22 ` Dominick Grift
[not found] ` <4D471319.2000907@tresys.com>
2011-01-31 21:18 ` Guido Trentalancia
2011-02-02 23:52 ` Martin Orr
2011-02-03 0:04 ` Guido Trentalancia
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=1295829820.3862.59.camel@tesla.lan \
--to=guido@trentalancia.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.