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, 4 Oct 2006 08:36:46 -0400
From:	"John W. Linville" <linville@...driver.com>
To:	Sean <seanlkml@...patico.ca>
Cc:	jt@....hp.com, Theodore Tso <tytso@....edu>,
	Jeff Garzik <jeff@...zik.org>,
	Linus Torvalds <torvalds@...l.org>,
	Lee Revell <rlrevell@...-job.com>,
	Alessandro Suardi <alessandro.suardi@...il.com>,
	Norbert Preining <preining@...ic.at>, hostap@...oo.com,
	linux-kernel@...r.kernel.org, johannes@...solutions.net
Subject: Re: wpa supplicant/ipw3945, ESSID last char missing

On Tue, Oct 03, 2006 at 08:36:46PM -0400, Sean wrote:
> On Tue, 3 Oct 2006 17:30:31 -0700
> Jean Tourrilhes <jt@....hp.com> wrote:
> 
> > 	How does that happen in practice ? Kernel has no clue on what
> > userpace version is running.
> > 
> 
> Ted mentioned that the way it works for stat is that userspace requests
> an API version and the kernel delivers it.  So old versions request old
> API and new versions request new API.  You only ever _add_ new API, and
> never remove older versions.

I think the point is that the API currently has no such facility.
Adding a new set of WE ioctls is unpalatable, both for general
ioctl-haters and because the WE ioctl collection is quite broad.
Maybe that could be solved by forcing the new WE stuff to use
the netlink-based WE facilities, but then you are expanding the
compatibility nightmare for whatever replaces WE.

John
-- 
John W. Linville
linville@...driver.com
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ