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]

Date:	Fri, 9 Jul 2010 10:10:58 -0700
From:	Steve Fink <sphink@...il.com>
To:	"Loke, Chetan" <Chetan.Loke@...scout.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

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? 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.)

But perhaps there *is* an equivalent: what about (ab)using bridges?
Create a set of bridges and bind each one to a single NIC. You can
name the bridges whatever you want, and set up the mapping through
arbitrary logic.
--
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/