netdev - Re: [PATCH iproute2] ip tap: Simplify add 'tap' device w/o mode

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:	Sun, 1 Mar 2015 14:07:15 -0800
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	Vadim Kochan <vadim4j@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH iproute2] ip tap: Simplify add 'tap' device w/o mode

On Sat, 28 Feb 2015 11:59:46 +0200
Vadim Kochan <vadim4j@...il.com> wrote:

> From: Vadim Kochan <vadim4j@...il.com>
> 
> It allows add 'tap' device w/o specify mode:
> 
>     # ip tap add tap0
> 
> instead of return error message.
> 
> Signed-off-by: Vadim Kochan <vadim4j@...il.com>

No. mode should not depend on device name.

Also, I noticed that reading kernel code it is possible to
create a broken tun device if type is not set.

--
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