From: David Ahern <dsahern@gmail.com>
To: Kevin Cernekee <cernekee@chromium.org>, davem@davemloft.net
Cc: johannes.berg@intel.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] netlink: Add netns check on taps
Date: Tue, 5 Dec 2017 19:19:49 -0700 [thread overview]
Message-ID: <ca498c45-a37a-ec2e-1faa-5a6ff81384f5@gmail.com> (raw)
In-Reply-To: <1512513982-20407-1-git-send-email-cernekee@chromium.org>
On 12/5/17 3:46 PM, Kevin Cernekee wrote:
> Currently, a nlmon link inside a child namespace can observe systemwide
> netlink activity. Filter the traffic so that in a non-init netns,
> nlmon can only sniff netlink messages from its own netns.
>
> Test case:
>
> vpnns -- bash -c "ip link add nlmon0 type nlmon; \
> ip link set nlmon0 up; \
> tcpdump -i nlmon0 -q -w /tmp/nlmon.pcap -U" &
> sudo ip xfrm state add src 10.1.1.1 dst 10.1.1.2 proto esp \
> spi 0x1 mode transport \
> auth sha1 0x6162633132330000000000000000000000000000 \
> enc aes 0x00000000000000000000000000000000
> grep abc123 /tmp/nlmon.pcap
>
> Signed-off-by: Kevin Cernekee <cernekee@chromium.org>
> ---
> net/netlink/af_netlink.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/net/netlink/af_netlink.c b/net/netlink/af_netlink.c
> index b9e0ee4..88381a2 100644
> --- a/net/netlink/af_netlink.c
> +++ b/net/netlink/af_netlink.c
> @@ -253,6 +253,11 @@ static int __netlink_deliver_tap_skb(struct sk_buff *skb,
> struct sock *sk = skb->sk;
> int ret = -ENOMEM;
>
> + if (!net_eq(dev_net(dev), sock_net(sk)) &&
> + !net_eq(dev_net(dev), &init_net)) {
Why is init_net special? Seems like snooping should be limited to the
namespace you are in.
next prev parent reply other threads:[~2017-12-06 2:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 22:46 [PATCH] netlink: Add netns check on taps Kevin Cernekee
2017-12-06 2:19 ` David Ahern [this message]
2017-12-06 3:14 ` Kevin Cernekee
2017-12-06 19:40 ` David Miller
2017-12-06 20:51 ` Daniel Borkmann
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=ca498c45-a37a-ec2e-1faa-5a6ff81384f5@gmail.com \
--to=dsahern@gmail.com \
--cc=cernekee@chromium.org \
--cc=davem@davemloft.net \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).