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
| ||
|
Date: Wed, 9 Aug 2017 18:10:27 +0200 From: Andrew Lunn <andrew@...n.ch> To: Vitaly Kuznetsov <vkuznets@...hat.com> Cc: ???????????? <hideaki.yoshifuji@...aclelinux.com>, network dev <netdev@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Stephen Hemminger <stephen@...workplumber.org> Subject: Re: [PATCH RFC net-next] net: Allow name change of IFF_UP interfaces > I understand the 'legacy' concern but at the same time we don't want to > have aftificial limitations too. Name change, in particular, doesn't > happen 'under the hood' -- someone privileged enough needs to request > the change. > > Can you think of any particular real world scenarios which are broken by > the change? How about: man 8 dhclient-script The interface name is passed in $interface to the scripts. Do we get the old name or the new name? I suspect scripts are going to break if they are given the old name, which no longer exists. Andrew
Powered by blists - more mailing lists