From: Stephen Hemminger <stephen@networkplumber.org>
To: Mahesh Bandewar <maheshb@google.com>
Cc: Jay Vosburgh <j.vosburgh@gmail.com>,
Andy Gospodarek <andy@greyhouse.net>,
Veaceslav Falico <vfalico@gmail.com>,
Nikolay Aleksandrov <nikolay@redhat.com>,
David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
Maciej Zenczykowski <maze@google.com>
Subject: Re: [PATCH next v0] bonding: Display LACP info only to CAP_SYS_ADMIN capable user
Date: Thu, 11 Jun 2015 14:09:35 -0700 [thread overview]
Message-ID: <20150611140935.6533fb7c@urahara> (raw)
In-Reply-To: <1433981996-6010-1-git-send-email-maheshb@google.com>
On Wed, 10 Jun 2015 17:19:56 -0700
Mahesh Bandewar <maheshb@google.com> wrote:
> Actor and Partner details can be accessed via proc-fs and sys-fs
> entries. These interfaces are world readable at this moment. The
> earlier patch-series made the LACP communication secure to avoid
> nuisance attack from within the same L2 domain but it did not
> prevent "someone unprivileged" looking at that information on host
> and perform the same act.
>
> This patch essentially avoids spitting those entries if the user
> in question does not have enough privileges.
>
> Signed-off-by: Mahesh Bandewar <maheshb@google.com>
I would think you want CAP_NET_ADMIN for this?
next prev parent reply other threads:[~2015-06-11 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 0:19 [PATCH next v0] bonding: Display LACP info only to CAP_SYS_ADMIN capable user Mahesh Bandewar
2015-06-11 21:09 ` Stephen Hemminger [this message]
2015-06-11 22:22 ` David Miller
2015-06-12 17:53 ` Mahesh Bandewar
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=20150611140935.6533fb7c@urahara \
--to=stephen@networkplumber.org \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.com \
--cc=maheshb@google.com \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@redhat.com \
--cc=vfalico@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox