From: Michael Kerrisk <mtk.manpages@googlemail.com>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: James Morris <jmorris@namei.org>,
lkml <linux-kernel@vger.kernel.org>,
SELinux <selinux@tycho.nsa.gov>,
linux-security-module@vger.kernel.org,
Stephen Smalley <sds@epoch.ncsc.mil>,
Kees Cook <kees.cook@canonical.com>,
Andrew Morgan <morgan@kernel.org>,
"Christopher J. PeBenito" <cpebenito@tresys.com>,
Eric Paris <eparis@parisplace.org>
Subject: Re: [PATCH] Define CAP_SYSLOG
Date: Sun, 14 Mar 2010 06:18:50 +0100 [thread overview]
Message-ID: <cfd18e0f1003132118y21bd71band2d07ae85c8d4c9@mail.gmail.com> (raw)
In-Reply-To: <20100312205537.GA1091@us.ibm.com>
> There is one downside to this patch: If some site or distro currently
> has syslogd/whatever running as a non-root user with cap_sys_admin+pe,
> then it will need to be changed to run with cap_syslog+pe. I don't
> know if there are such sites, or if that concern means we should take
> a different approach to introducing this change, or simply refuse this
> change.
*If* this is a problem, would the way to address it not be to permit
syslog if the caller has *either* CAP_SYS_ADMIN or CAP_SYSLOG? (The
only weakness I see in this idea is that it fails to lighten the
hugely overlaoded CAP_SYS_ADMIN.)
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface" http://blog.man7.org/
next prev parent reply other threads:[~2010-03-14 5:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 20:55 [PATCH] Define CAP_SYSLOG Serge E. Hallyn
2010-03-12 20:55 ` Serge E. Hallyn
2010-03-12 20:58 ` [refpolicy] [PATCH refpolicy] add capability2:syslog perm Serge E. Hallyn
2010-03-14 5:18 ` Michael Kerrisk [this message]
2010-03-14 5:35 ` [PATCH] Define CAP_SYSLOG Serge E. Hallyn
2010-03-14 5:35 ` Serge E. Hallyn
2010-03-15 1:16 ` Matthew Helsley
2010-03-15 4:24 ` Serge E. Hallyn
2010-03-15 4:24 ` Serge E. Hallyn
2010-10-31 22:36 ` Console Login and SSH Login Security Contexts Hasan Rezaul-CHR010
2010-11-01 15:59 ` Christopher J. PeBenito
2010-11-01 21:11 ` Hasan Rezaul-CHR010
2010-11-02 7:48 ` HarryCiao
2010-11-02 13:36 ` Christopher J. PeBenito
2010-11-02 18:12 ` Hasan Rezaul-CHR010
2010-11-01 5:27 ` Format of file_contexts file Hasan Rezaul-CHR010
2010-11-01 16:02 ` Christopher J. PeBenito
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=cfd18e0f1003132118y21bd71band2d07ae85c8d4c9@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=cpebenito@tresys.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=kees.cook@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=morgan@kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=sds@epoch.ncsc.mil \
--cc=selinux@tycho.nsa.gov \
--cc=serue@us.ibm.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.