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] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 4 Feb 2013 09:56:36 -0800
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	nicolas.dichtel@...nd.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH iproute2] iplink: display the value of IFLA_PROMISCUITY

On Mon, 04 Feb 2013 18:27:51 +0100
Nicolas Dichtel <nicolas.dichtel@...nd.com> wrote:

> Le 04/02/2013 18:04, Stephen Hemminger a écrit :
> > On Mon, 28 Jan 2013 06:47:56 -0800
> > Nicolas Dichtel <nicolas.dichtel@...nd.com> wrote:
> >
> >> This is usefull to know the 'real' status of an interface (the flag IFF_PROMISC
> >> is exported by the kernel only when the user set it explicitly, for example it
> >> will not be exported when a tcpdump is running).
> >>
> >> Note that I add a space after qlen (instead of before promiscuity) to be
> >> coherent with the rest of the code.
> >>
> >> Signed-off-by: Nicolas Dichtel <nicolas.dichtel@...nd.com>
> >> ---
> >>   ip/ipaddress.c | 5 ++++-
> >>   1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > The idea is good, but I can't accept in the current form.
> > The problem with this is that it violates the unwritten assumption that the output
> > of ip command should be the arguments used to setup that interface. There were even
> > some VPN's that depended on that.
> >
> Would it be acceptable to display this information when '-d' (ip -details link) 
> is provided by the user?

Yeah, that seems to be where such things end up.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ