From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: stable@kernel.org,
linux-wireless <linux-wireless@vger.kernel.org>,
Jean Tourrilhes <jt@hpl.hp.com>
Subject: Re: [PATCH] fix information leak in wireless extensions on 64-bit platforms
Date: Fri, 23 Mar 2007 11:42:37 -0400 [thread overview]
Message-ID: <20070323154237.GB3882@tuxdriver.com> (raw)
In-Reply-To: <1174657362.3366.6.camel@johannes.berg>
On Fri, Mar 23, 2007 at 02:42:42PM +0100, Johannes Berg wrote:
> On Fri, 2007-03-23 at 14:40 +0100, Johannes Berg wrote:
> > Wireless extensions on 64-bit platforms leak information from the kernel
> > stack due to padding in structs that is copied. This affects any
> > wireless event stream including scan results and so hence is available
> > to unprivileged users.
>
> Ignore this patch, I see Jean just posted one as well :)
Hmmm...I seem to have missed it. Perhaps I was too quick w/ the 'd'
this morning? :-)
Jean, could you bounce me another copy?
Thanks,
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-03-23 16:22 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 [this message]
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
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=20070323154237.GB3882@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=johannes@sipsolutions.net \
--cc=jt@hpl.hp.com \
--cc=linux-wireless@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.