From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 1/1] Allow userdomains to send syslog messages
Date: Wed, 24 Aug 2011 21:50:06 +0200 [thread overview]
Message-ID: <20110824195005.GA3011@siphos.be> (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.
>
The one that triggered the creation of the patch was to support bashlogger
(feature of bash that logs all activity to the system logger). Another one
we had a way back (but I just informed the user how to allow it for himself
then) was for a chat client (i think it was weechatter, but the case was
applicable to others as well) configured to log things to the system log.
I don't mind if this is deemed a bit too intrusive for regular purposes.
Wkr,
Sven Vermeulen
prev parent reply other threads:[~2011-08-24 19:50 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
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 [this message]
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=20110824195005.GA3011@siphos.be \
--to=sven.vermeulen@siphos.be \
--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.