From: domg472@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 1/1] Allow userdomains to send syslog messages
Date: Wed, 24 Aug 2011 15:15:09 +0200 [thread overview]
Message-ID: <20110824131507.GA25303@localhost.localdomain> (raw)
In-Reply-To: <4E54F828.8020200@tresys.com>
On Wed, Aug 24, 2011 at 09:10:00AM -0400, Christopher J. PeBenito wrote:
> On 08/23/11 06:57, Sven Vermeulen wrote:
> > Some applications that run within the user domain send messages to the syslog
> > daemon (for instance through the syslog() function). This patch allows the
> > userdomain to write to the devlog_t socket and interact properly with the
> > syslog daemon.
>
> Do you have some examples? My initial reaction is definitely not
> merged, as I don't want users to be able to flood the system logs.
I do, the git-daemon run by users can be configured to use syslog. I allowed this by default in my git policy. Would you prefer a boolean "git_session_daemon_can_syslog" instead of allowing it by default?
>
>
> > Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
> > ---
> > policy/modules/system/userdomain.if | 2 ++
> > 1 files changed, 2 insertions(+), 0 deletions(-)
> >
> > diff --git a/policy/modules/system/userdomain.if b/policy/modules/system/userdomain.if
> > index c6d3cc8..17abfcf 100644
> > --- a/policy/modules/system/userdomain.if
> > +++ b/policy/modules/system/userdomain.if
> > @@ -965,6 +965,8 @@ template(`userdom_unpriv_user_template', `
> > # cjp: why?
> > files_read_kernel_symbol_table($1_t)
> >
> > + logging_send_syslog_msg($1_t)
> > +
> > ifndef(`enable_mls',`
> > fs_exec_noxattr($1_t)
> >
>
>
> --
> Chris PeBenito
> Tresys Technology, LLC
> www.tresys.com | oss.tresys.com
> _______________________________________________
> refpolicy mailing list
> refpolicy at oss.tresys.com
> http://oss.tresys.com/mailman/listinfo/refpolicy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20110824/b2a56548/attachment.bin
next prev parent reply other threads:[~2011-08-24 13:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 10:57 [refpolicy] [PATCH 1/1] Allow userdomains to send syslog messages Sven Vermeulen
2011-08-24 13:10 ` Christopher J. PeBenito
2011-08-24 13:15 ` Dominick Grift [this message]
2011-08-24 13:41 ` Christopher J. PeBenito
2011-08-24 13:51 ` Dominick Grift
2011-08-24 14:16 ` Christopher J. PeBenito
2011-08-24 14:31 ` Dominick Grift
2011-08-24 16:11 ` Christopher J. PeBenito
2011-08-24 16:23 ` Dominick Grift
2011-08-25 11:09 ` Christopher J. PeBenito
2011-08-25 11:21 ` Dominick Grift
2011-08-25 9:56 ` Dominick Grift
2011-08-24 19:50 ` Sven Vermeulen
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=20110824131507.GA25303@localhost.localdomain \
--to=domg472@gmail.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.