All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom <tom@lemuria.org>
To: selinux@tycho.nsa.gov
Subject: Re: policy under version control
Date: Sat, 29 Nov 2003 16:05:07 +0100	[thread overview]
Message-ID: <20031129160507.A9332@lemuria.org> (raw)
In-Reply-To: <20031129132619.GE26960@lukas.schuldei.com>; from andreas@schuldei.org on Sat, Nov 29, 2003 at 02:26:19PM +0100

On Sat, Nov 29, 2003 at 02:26:19PM +0100, Andreas Schuldei wrote:
> I find it tiresom and uneffective to make changes to policy
> without and easy way to feed my effords upstream. Actually i feel
> selinux stands and falls with a smoothly working policy. this
> needs attention and time of many, not just one.

I second that. I get frightened every time I update the policy because
I know it'll break half my local changes.

Also, the update process needs refinement. For one, I find it very
tiresome (and error-prone!) to not bundle packages.

For example, there are many policy files that we can be reasonably sure
will be part of EVERY system. I don't know many Linux systems that
wouldn't want the rules for mount and init, for example.

Why not just lump them into one bundle? Not one .te file, but one
installer question.


> i would therefor suggest to create a public readabel repository
> against which one can update and also some scripts for mailing
> back/submitting to the repository(?) the changes needed to make
> the subsystems work.

Some of the more modern cvs replacements seem suited for this. Arch and
Subversion both might work great with a proper setup.


Also, whatever happened to Collins attempt to automate the install?


-- 
http://web.lemuria.org/pubkey.html
pub  1024D/2D7A04F5 2002-05-16 Tom Vogt <tom@lemuria.org>
     Key fingerprint = C731 64D1 4BCF 4C20 48A4  29B2 BF01 9FA1 2D7A 04F5

--
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:[~2003-11-29 15:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-29 13:26 policy under version control Andreas Schuldei
2003-11-29 15:05 ` Tom [this message]
2003-11-29 21:35   ` Russell Coker
2003-12-01 15:13 ` Stephen Smalley
2003-12-01 19:28   ` Tom
2003-12-01 22:53     ` Dale Amon
2003-12-02  3:30     ` Russell Coker
2003-12-02  7:08       ` Tom
2003-12-02  9:59         ` Brian May
2003-12-06 15:57           ` Colin Walters
2003-12-07 11:30           ` Tom
2003-12-07 13:41             ` Andreas Schuldei
2003-12-07 13:44               ` Russell Coker
2003-12-07 13:59                 ` Tom
2003-12-07 13:57               ` Tom
2003-12-02 14:58         ` Colin Walters
2003-12-02 18:52           ` Tom
2003-12-03 13:34             ` Tom
  -- strict thread matches above, loose matches on Subject: below --
2003-12-03 15:36 Karl MacMillan
2003-12-03 16:56 ` Serge E. Hallyn

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=20031129160507.A9332@lemuria.org \
    --to=tom@lemuria.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.