netdev - Re: [RFC] Alternative hidden netwirk device interface

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:	Wed, 31 Jan 2007 19:26:47 +0100
From:	Jiri Benc <jbenc@...e.cz>
To:	Stephen Hemminger <shemminger@...ux-foundation.org>
Cc:	netdev@...r.kernel.org,
	"John W. Linville" <linville@...driver.com>,
	David Miller <davem@...emloft.net>
Subject: Re: [RFC] Alternative hidden netwirk device interface

On Mon, 29 Jan 2007 14:09:58 -0800, Stephen Hemminger wrote:
> Change to allow register_netdevice() to be called with a blank name.
> If name is blank, it is not put in name hash list, and doesn't
> show up in /sys or /proc

What about things like neigh_sysctl_register which expects nonempty dev
name or rtnetlink_event which sends a RTM_NEWLINK event (I doubt that
listeners are prepared for nonempty dev name)?

Also, if the interface has ifindex assigned it is accessible from user
space (although it's unlikely anybody would call anything on it) - what
should be the correct result of e.g. SIOCGIFNAME?

Thanks,

 Jiri

-- 
Jiri Benc
SUSE Labs
-
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