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
| ||
|
Message-ID: <461B7D9A.50902@trash.net> Date: Tue, 10 Apr 2007 14:05:46 +0200 From: Patrick McHardy <kaber@...sh.net> To: Johannes Berg <johannes@...solutions.net> CC: "Eric W. Biederman" <ebiederm@...ssion.com>, David Miller <davem@...emloft.net>, akpm@...ux-foundation.org, dim@...nvz.org, netdev@...r.kernel.org, jgarzik@...ox.com, containers@...ts.osdl.org, kuznet@....inr.ac.ru, shemminger@...ux-foundation.org, greearb@...delatech.com Subject: Re: [PATCH] net: Add etun driver Johannes Berg wrote: > Fair enough. Then the question however remains whether wireless should > try to do all things it needs in one or try leveraging multiple things > from other places. Thoughts? I know too little about wireless to judge really this. My opinion is that if it is possible to add and configure an interface (even if only for simple cases) without knowledge about driver internals by setting a few parameters, it would probably make sense to use RTM_NEWLINK as well. If a userspace daemon or complex knowledge of driver internals is needed, it probably should stay seperated. So simply put: if I can implement support for "ip wireless add dev wlan0 mode managed essid ... key ..." in less than 100 lines and get a working connection afterwards, it seems worth it. - 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
Powered by blists - more mailing lists