From: Tom <tom@lemuria.org>
To: selinux@tycho.nsa.gov
Subject: Re: mysql policy
Date: Tue, 29 Oct 2002 20:49:14 +0100 [thread overview]
Message-ID: <20021029204914.B16084@lemuria.org> (raw)
In-Reply-To: <Pine.GSO.4.33.0210291407460.29605-100000@raven>; from sds@tislabs.com on Tue, Oct 29, 2002 at 02:16:52PM -0500
On Tue, Oct 29, 2002 at 02:16:52PM -0500, Stephen Smalley wrote:
> >+allow initrc_t mysqld_db_t:dir { write };
>
> I'm not clear as to the purpose of this rule in isolation. Without other
> directory permissions (e.g. add_name, remove_name), directory write
> permission is useless. What exactly is the rc script doing to this
> directory?
If I remember correctly, it's tee'ing any errors during startup to an
error log file that is located there. I'm working on this anyway, so if
you don't feel happy with it, just wait until I have a more refined
policy to offer. For some reason, though, adding this rule makes it
work on my system.
--
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.
next prev parent reply other threads:[~2002-10-29 19:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 10:01 mysql policy Tom
2002-10-28 12:24 ` Russell Coker
2002-10-28 12:58 ` Tom
2002-10-28 13:47 ` Russell Coker
2002-10-28 14:05 ` Tom
2002-10-28 15:12 ` Tom
2002-10-29 19:16 ` Stephen Smalley
2002-10-29 19:49 ` Tom [this message]
2002-10-29 20:07 ` Stephen Smalley
2002-10-30 6:51 ` Tom
2002-10-30 14:32 ` Tom
-- strict thread matches above, loose matches on Subject: below --
2002-10-30 9:35 Tom
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=20021029204914.B16084@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.