netdev - Re: [PATCH iproute2] utils: do not be restrictive about alternate network device names

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: <fa3ba651-67a8-4cde-b9d2-da2d89111341@gmail.com>
Date: Wed, 7 Jan 2026 09:54:18 -0700
From: David Ahern <dsahern@...il.com>
To: Stephen Hemminger <stephen@...workplumber.org>, netdev@...r.kernel.org
Subject: Re: [PATCH iproute2] utils: do not be restrictive about alternate
 network device names

On 12/21/25 10:49 AM, Stephen Hemminger wrote:
> The kernel does not impose restrictions on alternate interface
> names; therefore ip commands should not either.
> 
> This allows colon, slash, even .. as alternate names.
> 
> Signed-off-by: Stephen Hemminger <stephen@...workplumber.org>
> ---
>  lib/utils.c | 21 +++++++++++----------
>  1 file changed, 11 insertions(+), 10 deletions(-)
> 

applied to iproute2-next. I wonder if the checks should be removed from
iproute2 and left to the kernel logic to decide if the name is valid.