From: Daniel J Walsh <dwalsh@redhat.com>
To: Bill McCarty <bmccarty@pt-net.net>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: RHEL 3 policy and policy-sources RPMs
Date: Sun, 18 Jan 2004 22:07:26 -0500 [thread overview]
Message-ID: <400B49EE.2080502@redhat.com> (raw)
In-Reply-To: <222304176.1074345262@[192.168.0.100]>
Bill McCarty wrote:
> Hi all,
>
> (1) I'm setting up another SELinux host on RHEL3, in addition to the
> one I successfully set up a few days back. I downloaded RPMs from
> people.redhat.com, but find that prelink.te and several other TE files
> (rpm.te, slocate.te) have syntax errors that prevent me from
> successfully making the policy. For instance:
>
> ERROR 'syntax error' at token '-' on line 102125:
Sorry about that a couple of packages had fallen behind on the RHEL3
tree. You need to upgrade your version of Check Policy. The "-XYZ"
syntax has been added to say get everything in this category except XYZ.
>
>
>> allow prelink_t {root_dir_type file_type -shadow_t} :{ file dir lnk_file
>> } { getattr read}; /usr/bin/checkpolicy: error(s) encountered while
>> parsing configuration
>
>
> It appears that an unwanted dash has been introduced. Unfortunately,
> after deleting the offending dashes, I ran into other problems:
>
>> security: 3 users, 5 roles, 1066 types
>> security: 30 classes, 134765 rules
>> assertion on line 130825 violated by allow rpm_t shadow_t:file {
>> relabelfrom relabelto }; assertion on line 130824 violated by allow
>> prelink_t shadow_t:file { read }; assertion on line 130824 violated by
>> allow rpm_t shadow_t:file { relabelfrom relabelto }; assertion on line
>> 130824 violated by allow locate_t shadow_t:file { read }; make: ***
>> [/etc/security/selinux/policy.15] Error 1
>
>
> As a temporary expedient, I changed the relevant lines of assert.te to:
>
> neverallow ~{ auth auth_write } shadow_t:file ~{ getattr read
> relabelfrom relabelto };
> neverallow ~auth_write shadow_t:file ~{ read getattr lock ioctl
> relabelfrom relabelto};
>
> After these changes, the policy compiles. I don't yet know how well it
> works.
>
> Obviously, I understand that this policy is under active development
> and I don't want to seem to whine about such problems. But, are there
> better or worse times for users to work with it <g>? If so, I'd like
> to get in sync.
>
I try to keep everything in sync, and most of the active work is being
done for Fedora Core. But I will try to keep everything in sync on
RHEL3 in the future.
> (2) Also, I'm curious why some policy source files are found in both
> the policy and policy-sources RPMs.
>
I didn't know that I will look.
> Thanks, in any case, to Daniel and other who're working on this policy!
>
> Cheers,
>
> ---------------------------------------------------
> Bill McCarty
>
> --
> 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.
--
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-01-19 3:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 21:14 RHEL 3 policy and policy-sources RPMs Bill McCarty
2004-01-19 3:07 ` Daniel J Walsh [this message]
2004-01-19 3:12 ` Bill McCarty
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=400B49EE.2080502@redhat.com \
--to=dwalsh@redhat.com \
--cc=bmccarty@pt-net.net \
--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.