From: Michael Buesch <mb@bu3sch.de>
To: jt@hpl.hp.com
Cc: Chris Wright <chrisw@sous-sol.org>,
Johannes Berg <johannes@sipsolutions.net>,
linux-wireless <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>,
stable@kernel.org
Subject: Re: [stable] [PATCH] fix information leak in wireless extensions on 64-bit platforms
Date: Sat, 24 Mar 2007 17:50:21 +0100 [thread overview]
Message-ID: <200703241750.21630.mb@bu3sch.de> (raw)
In-Reply-To: <20070323205142.GA5363@bougret.hpl.hp.com>
On Friday 23 March 2007 21:51, Jean Tourrilhes wrote:
> On Fri, Mar 23, 2007 at 09:27:17PM +0100, Michael Buesch wrote:
> > On Friday 23 March 2007 21:00, Jean Tourrilhes wrote:
> >
> > I finally have an USB ZD stick now, too. So I can test stuff, too.
> > Should I test this somehow?
>
> Ok, here it goes.
> Pick the latest version of wtools. You may want to compile it
> static to avoid the need to install it.
>
> To test the wpa patch, you need 32 bit userspace on 64 bit
> kernel, and you need to try :
> 'iwlist genie'
>
> To test the leak patch, you need a 64 kernel and any
Ok, so the most important question: Where to get the latest
versions of these patches? :)
I kind of lost track of what was agreed on and what's latest, etc..
Some link to the mail?
> userspace. You need two changes to enable the debugging code.
> 1) Put '#define DEBUG 1' on top of iwlib.c.
> 2) Change '#if 0' to '#if 1' line 783 of iwlist.c, at the
> bottom of print_scanning_info().
> Compile everything.
> If you do a 'iwlist scan', it should dump the full content of
> the stream. The first 4 bytes is the header (length + type). The next
> 4 bytes on 64 bits should be all zero.
> This is what I don't want to see :
> [19:00:1B:8B:50:8A:35:E0:09:00:01:00:50:8A:35:F0:47:6F:6C:6F:73:4E:65:74:7A
> This is what I want to see :
> [19:00:1B:8B:00:00:00:00:09:00:01:00:50:8A:35:F0:47:6F:6C:6F:73:4E:65:74:7A
> Note that du to endian considerations you may have some of
> your bytes swapped.
>
> > Greetings Michael.
>
> Good luck...
>
> Jean
>
>
--
Greetings Michael.
next prev parent reply other threads:[~2007-03-24 16:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 9:06 [PATCH] fix information leak in wireless extensions on 64-bit platforms Johannes Berg
2007-03-23 13:42 ` Johannes Berg
2007-03-23 15:42 ` John W. Linville
2007-03-23 16:24 ` Jean Tourrilhes
2007-03-23 15:48 ` Jean Tourrilhes
2007-03-23 15:56 ` Johannes Berg
2007-03-23 16:13 ` Jean Tourrilhes
2007-03-23 16:35 ` [stable] " Greg KH
2007-03-23 16:53 ` Michael Buesch
2007-03-23 17:57 ` Jean Tourrilhes
2007-03-23 19:36 ` [stable] " Chris Wright
2007-03-23 20:00 ` Jean Tourrilhes
2007-03-23 20:05 ` Johannes Berg
2007-03-23 20:27 ` Michael Buesch
2007-03-23 20:31 ` Johannes Berg
2007-03-23 20:51 ` Jean Tourrilhes
2007-03-24 16:50 ` Michael Buesch [this message]
2007-03-26 15:45 ` Jean Tourrilhes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200703241750.21630.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=chrisw@sous-sol.org \
--cc=johannes@sipsolutions.net \
--cc=jt@hpl.hp.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=stable@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).