From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Fix typo in /etc/selinux/*/contexts/sepgsql_contexts
Date: Tue, 22 Mar 2011 09:34:57 -0400 [thread overview]
Message-ID: <4D88A581.8050102@tresys.com> (raw)
In-Reply-To: <AANLkTikShhaegtXARP72M0AY4HX+40tOpueccWbq5OwD@mail.gmail.com>
On 03/21/11 17:59, Kohei KaiGai wrote:
> I found my typo in the sepgsql_contexts file.
>
> In the initial setting up of SE-PostgreSQL, it alerts on an invalid
> object type db_blobs,
> however, it should be "db_blob", not "db_blobs".
> Please apply this fix.
I didn't see a patch, so I fixed it manually.
> (Please ignore warnings about db_language. It is not a problem of
> refpolicy side.)
>
> [kaigai at vmlinux ~]$ postgres --single -F -O -c exit_on_error=true postgres \
> < /usr/local/pgsql/share/contrib/sepgsql.sql > /dev/null
> /etc/selinux/targeted/contexts/sepgsql_contexts: line 33 has invalid
> object type db_blobs
> /etc/selinux/targeted/contexts/sepgsql_contexts: line 36 has invalid
> object type db_language
> /etc/selinux/targeted/contexts/sepgsql_contexts: line 37 has invalid
> object type db_language
> /etc/selinux/targeted/contexts/sepgsql_contexts: line 38 has invalid
> object type db_language
> /etc/selinux/targeted/contexts/sepgsql_contexts: line 39 has invalid
> object type db_language
> /etc/selinux/targeted/contexts/sepgsql_contexts: line 40 has invalid
> object type db_language
>
> Thanks,
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2011-03-22 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 21:59 [refpolicy] Fix typo in /etc/selinux/*/contexts/sepgsql_contexts Kohei KaiGai
2011-03-22 13:34 ` Christopher J. PeBenito [this message]
2011-03-22 21:17 ` Kohei KaiGai
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=4D88A581.8050102@tresys.com \
--to=cpebenito@tresys.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.