netdev - Re: [PATCH net-next] net: packet: allow bind to device which is !IFF

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20171220.150656.1052155984496301218.davem@davemloft.net>
Date:   Wed, 20 Dec 2017 15:06:56 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     cugyly@....com
Cc:     netdev@...r.kernel.org, Linyu.Yuan@...atel-sbell.com.cn
Subject: Re: [PATCH net-next] net: packet: allow bind to device which is
 !IFF_UP

From: yuan linyu <cugyly@....com>
Date: Wed, 20 Dec 2017 21:20:49 +0800

> From: yuan linyu <Linyu.Yuan@...atel-sbell.com.cn>
> 
> this try to allow tcpdump to capture packet once device IFF_UP
> 
> Signed-off-by: yuan linyu <Linyu.Yuan@...atel-sbell.com.cn>

I don't think this is such a great idea.

Even if it "works":

1) The behavior goes back decades, this means real applications can
   be broken by this change.

2) The feedback is useful, if I ran tcpdump on the wrong interface
   I'd like to get this error if the interface I mistakenly chose
   was done in order to help me figure this out.