From: Steven Harp <steven.harp@adventiumlabs.org>
To: SELinux <SELinux@tycho.nsa.gov>
Subject: Re: What policy is the system running?
Date: Wed, 3 Nov 2004 11:28:48 -0600 [thread overview]
Message-ID: <200411031129.01034.steven.harp@adventiumlabs.org> (raw)
In-Reply-To: <20041103160311.51639.qmail@web50604.mail.yahoo.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 03 November 2004 10:03 am, Steve G wrote:
> >We could do an md5 checksum of the binary policy as it is written to
> >/selinuxfs/load then export this via /selinux/policy_md5sum.
>
> I'm not sure I like this approach...they may have just recompiled a policy
> (overwriting the one in memory) and have either no policy that matches or perhaps
> multiple policies that match.
Agreed. The policyname approach alluded earlier would be more
useful. Policy author gets to pick a name, version numbers etc,
supplemented by automatic information about when/where compiled.
This would convey the useful information for management. Working with
a set of machines running various different policies under continuous
development, I can testify this sort of feature would really be
valued. I'd speculate this much would be easy to add to /selinux fs.
Steve H
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQFBiRVVPcFX9H2zuSkRAm/+AJ4w5273zTrHRYhIa8NJaneIGu8dbgCgjrhp
s5NvovzYfUgTVV4GAah3F9c=
=BJPU
-----END PGP SIGNATURE-----
--
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.
next prev parent reply other threads:[~2004-11-03 17:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 19:23 What policy is the system running? Daniel J Walsh
2004-11-02 22:01 ` James Morris
2004-11-03 16:03 ` Steve G
2004-11-03 17:28 ` Steven Harp [this message]
2004-11-03 18:37 ` Karl MacMillan
2004-11-03 18:51 ` Steve G
2004-11-03 19:38 ` Stephen Smalley
2004-11-03 22:55 ` Daniel J Walsh
2004-11-04 14:38 ` Stephen Smalley
2004-11-02 22:13 ` Karl MacMillan
2004-11-03 1:28 ` Chris PeBenito
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=200411031129.01034.steven.harp@adventiumlabs.org \
--to=steven.harp@adventiumlabs.org \
--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.