From: Evgeniy Polyakov <zbr@ioremap.net>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Matt Helsley <matthltc@us.ibm.com>
Subject: Re: [PATCH] proc connector: reject unprivileged listener bumps
Date: Tue, 26 Feb 2013 12:46:06 +0400 [thread overview]
Message-ID: <20130226084606.GA21048@ioremap.net> (raw)
In-Reply-To: <20130226073225.GA15489@www.outflux.net>
Hi
On Mon, Feb 25, 2013 at 11:32:25PM -0800, Kees Cook (keescook@chromium.org) wrote:
> While PROC_CN_MCAST_LISTEN/IGNORE is entirely advisory, it was possible
> for an unprivileged user to turn off notifications for all listeners by
> sending PROC_CN_MCAST_IGNORE. Instead, require the same privileges as
> required for a multicast bind.
Sounds resonable.
Not sure whether this is a candidate for stable release, but otherwise
Acked-by: Evgeniy Polyakov <zbr@ioremap.net>
--
Evgeniy Polyakov
next prev parent reply other threads:[~2013-02-26 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 7:32 [PATCH] proc connector: reject unprivileged listener bumps Kees Cook
2013-02-26 8:46 ` Evgeniy Polyakov [this message]
2013-02-26 17:24 ` Matt Helsley
2013-02-27 18:08 ` David Miller
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=20130226084606.GA21048@ioremap.net \
--to=zbr@ioremap.net \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthltc@us.ibm.com \
--cc=netdev@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.