From: "Serge E. Hallyn" <serge@hallyn.com>
To: david@lang.hm
Cc: "Serge E. Hallyn" <serge@hallyn.com>,
Gergely Nagy <algernon@balabit.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
James Morris <jmorris@namei.org>
Subject: Re: CAP_SYSLOG, 2.6.38 and user space
Date: Fri, 4 Feb 2011 16:03:46 +0000 [thread overview]
Message-ID: <20110204160346.GA17396@mail.hallyn.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1102031647150.30983@asgard.lang.hm>
Quoting david@lang.hm (david@lang.hm):
> I can see what you would want to allow for a syslog daemon to have
> CAP_SYSLOG without needing to have CAP_SYS_ADMIN, but why do you see
> it as important to deny the ability if someone has CAP_SYS_ADMIN?
Good point, most of its use is in going the other way.
-serge
next prev parent reply other threads:[~2011-02-04 16:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 11:39 CAP_SYSLOG, 2.6.38 and user space Gergely Nagy
2011-02-03 15:13 ` Alan Cox
2011-02-03 15:32 ` Serge E. Hallyn
2011-02-03 15:53 ` Gergely Nagy
2011-02-03 16:51 ` Serge E. Hallyn
2011-02-03 17:07 ` Gergely Nagy
2011-02-04 0:49 ` david
2011-02-04 8:03 ` Marc Koschewski
2011-02-04 8:40 ` Gergely Nagy
2011-02-04 11:08 ` Alan Cox
2011-02-04 16:03 ` Serge E. Hallyn [this message]
2011-02-03 15:54 ` Nick Bowler
2011-02-04 16:05 ` Serge E. Hallyn
2011-02-04 16:33 ` Gergely Nagy
2011-02-04 17:15 ` Serge E. Hallyn
2011-02-05 7:05 ` david
2011-02-06 1:18 ` Serge E. Hallyn
2011-02-09 21:23 ` Serge E. Hallyn
2011-02-09 21:28 ` Gergely Nagy
2011-02-09 21:34 ` david
2011-02-09 21:40 ` Gergely Nagy
2011-02-09 21:47 ` david
2011-02-09 22:04 ` Gergely Nagy
2011-02-09 22:27 ` david
2011-02-09 22:37 ` Gergely Nagy
2011-02-10 14:29 ` Serge E. Hallyn
2011-02-09 19:50 ` Gergely Nagy
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=20110204160346.GA17396@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=algernon@balabit.hu \
--cc=david@lang.hm \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
/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.