From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Joshua Brindle <method@gentoo.org>
Cc: Steve Grubb <sgrubb@redhat.com>, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: rpmlint
Date: Mon, 06 Nov 2006 11:03:40 -0500 [thread overview]
Message-ID: <1162829020.26148.44.camel@localhost.localdomain> (raw)
In-Reply-To: <454E6663.8070609@gentoo.org>
On Sun, 2006-11-05 at 17:32 -0500, Joshua Brindle wrote:
> Steve Grubb wrote:
> > Hi,
> >
> > Below is a patch that I am thinking about submitting to rpmlint. The main idea
> > of this patch is to catch places where people might be coding policy knowledge
> > into scripts. Chcon would require knowing some types in order to work. If the
> > types ever got changed, the script would break. Can anyone think of other
> > things we do not want to see in rpm scriplets?
> >
> > -Steve
> >
> >
> calling semanage thusly:
>
> semanage fcontext -a [any arguments here] /some/file
>
> actually any semanage command except *possibly* login and user, and I'm
> not sure they should be there either but someone may have an acceptable
> scenerio.
If we disallow this then what is the recommended way to allow an
application to ship a labeling only policy? We need to allow
applications to, for example, label a library as textrel_shlib_t without
forcing them to ship a policy module.
What if we added the ability to specify the store by name (i.e.,
semanage -s targeted fcontext -a . . . .). I think it should be
acceptable to make assumptions about what a well know policy contains.
Getting them to use semanage in this way would fix other problems - like
relabeling - without introducing unnecessary policy modules.
Karl
--
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:[~2006-11-06 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 13:16 rpmlint Steve Grubb
2006-11-05 22:32 ` rpmlint Joshua Brindle
2006-11-06 16:03 ` Karl MacMillan [this message]
2006-11-06 16:25 ` rpmlint Joshua Brindle
2006-11-06 16:37 ` rpmlint Karl MacMillan
2006-11-06 18:13 ` rpmlint Joshua Brindle
2006-11-06 18:28 ` rpmlint Karl MacMillan
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=1162829020.26148.44.camel@localhost.localdomain \
--to=kmacmillan@mentalrootkit.com \
--cc=method@gentoo.org \
--cc=selinux@tycho.nsa.gov \
--cc=sgrubb@redhat.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.