linux-kernel - RE: nic enumeration

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]

Message-ID: <D3F292ADF945FB49B35E96C94C2061B90C3CF4C5@nsmail.netscout.com>
Date:	Fri, 9 Jul 2010 14:23:26 -0400
From:	"Loke, Chetan" <Chetan.Loke@...scout.com>
To:	"Steve Fink" <sphink@...il.com>
Cc:	"Florian Weimer" <fweimer@....de>, <linux-net@...r.kernel.org>,
	"Matt Domsch" <Matt_Domsch@...l.com>,
	"Michael Di Domenico" <mdidomenico4@...il.com>,
	<linux-kernel@...r.kernel.org>, <kay.sievers@...y.org>
Subject: RE: nic enumeration

> -----Original Message-----
> From: Steve Fink [mailto:sphink@...il.com]
> Sent: July 09, 2010 1:11 PM
> To: Loke, Chetan
> Cc: Florian Weimer; linux-net@...r.kernel.org; Matt Domsch; Michael Di
> Domenico; linux-kernel@...r.kernel.org; kay.sievers@...y.org
> Subject: Re: nic enumeration
> 
> On Fri, Jul 9, 2010 at 9:27 AM, Loke, Chetan
<Chetan.Loke@...scout.com>
> wrote:
> > Ok, no renaming, I would like a reference. And symlink just doesn't
> work
> > w/ the udevadm trigger business. We've tried that already.
> >
> > What needs to be changed in udev etc to create a soft link? Any
place
> > where I should start digging and gotchas to lookout for?
> 
> By "soft link", I assume you're talking figuratively? 

Yes, I was using it loosely. symlink == I would like 'udev' to do the
linkage w/ the network-devices and create a reference to it.


> Soft (symbolic)
> links are a filesystem concept, implemented by filesystem-specific
> logic that knows how to read a filename out of an inode and restart
> lookup. In order for something similar to work for network devices,
> somebody would have had to explicitly implement similar functionality.
> (Symlinks are a big headache and source of security holes -- access
> control, loops, pointing to nonexistent files, etc. -- so there's a
> good reason to NOT have an equivalent for network devices.)
> 

Huh? If the 'ethX' interface doesn't exist just don't create the 'link'.
So are you saying there are no security issues with udev-symlinks for
other subsystems? Why is renaming allowed on the network-interface then?
Isn't that a problem? I don't see the driver re-registering their RX/TX
queues with the new-if-name.

May be I'm overlooking at something really obvious. But how are people
managing [pv]drivers with multiple vNICs in their VMs if they need a
consistent naming scheme?


Regards
Chetan Loke


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/