linux-kernel - Re: wpa supplicant/ipw3945, ESSID last char missing

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:	Thu, 5 Oct 2006 09:35:13 -0700
From:	Jean Tourrilhes <jt@....hp.com>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	Theodore Tso <tytso@....edu>,
	"John W. Linville" <linville@...driver.com>,
	Jeff Garzik <jeff@...zik.org>, jt@....hp.com,
	Linus Torvalds <torvalds@...l.org>,
	Lee Revell <rlrevell@...-job.com>,
	Alessandro Suardi <alessandro.suardi@...il.com>,
	Norbert Preining <preining@...ic.at>,
	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org
Subject: Re: wpa supplicant/ipw3945, ESSID last char missing

On Wed, Oct 04, 2006 at 09:49:39AM +0200, Johannes Berg wrote:
> On Tue, 2006-10-03 at 19:16 -0400, Theodore Tso wrote:
> 
> > OK, I'm going to ask a stupid question.  Why is the kernel<->wireless
> > driver interface have to be tied to the userspace<->wireless
> > interface?  
> 
> Haha. Because Jean thinks it isn't and thus everything is fine. But in
> reality it is.
> 
> > Is there some reason why this would be too hard to do with the current
> > interface?  
> 
> Yes: drivers are expected to mostly handle the ioctls directly without a
> layer between them and userspace.

	Once again, your facts are totally wrong about Wireless
Extensions.
	Have you ever looked at the code in the kernel ? I guarantee
you that adding whatever specific WE translation is quite easy. In
this precise case, this would only increase confusion, so this should
be considered bad API practice.
	Regards,

	Jean

-
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/