From: Dan Williams <dcbw@redhat.com>
To: Matteo Croce <rootkit85@yahoo.it>
Cc: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>,
Matthieu Castet <castet.matthieu@free.fr>,
Fabrice Bellet <fabrice@bellet.info>,
"John W. Linville" <linville@tuxdriver.com>,
PReDaCoN <alessandroferrari@gmail.com>,
Benjamin Reed <breed@users.sourceforge.net>,
Javier Achirica <achirica@users.sourceforge.net>,
Jean Tourrilhes <jt@hpl.hp.com>,
linux-wireless@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: airo WPA
Date: Wed, 07 Nov 2007 10:13:08 -0500 [thread overview]
Message-ID: <1194448388.23721.0.camel@localhost.localdomain> (raw)
In-Reply-To: <200711071559.47916.rootkit85@yahoo.it>
On Wed, 2007-11-07 at 15:59 +0100, Matteo Croce wrote:
> Il Wednesday 07 November 2007 15:41:00 hai scritto:
> > On Wed, 2007-11-07 at 15:15 +0100, Matteo Croce wrote:
> > > New patch against current git
> >
> > NAK at the moment; we've got too many patches for this floating around.
> > I'm currently working out some issues with WPA with a pull from
> > Matthieu's svn repo plus a set from Fabrice. There's an issue with that
> > set (that your patch also has) that causes WPA associations to fail
> > because frames are driver-MIC-ed at the wrong times. The patches also
> > have some style issues that I'd like to clean up.
> >
> > So here's what I'd like to do with the airo WPA patches. They need to
> > go through _one_ place. Either I'll volunteer the time to handle them
> > and people can feed them through me, or we need some other place where
> > people can coordinate the work. I'm happy to push this stuff through
> > since it seems like most of the dual-mode issues have been solved.
> >
> > The immediate bug is that the driver mis-MICs the first few EAPOL frames
> > that come back during the 4-way handshake, failing the WPA association
> > for PCMCIA cards at least. I haven't tested with my mini-PCI part yet
> > and won't until this can be fixed. Once that appears to work, I'd like
> > to run through a bunch of setups and make sure the driver behaves as
> > expected for both WPA-capable and non-WPA-capable firmware versions, and
> > with a number of different RADIUS setups and encryption modes including
> > Dynamic WEP.
> >
> > Dan
> >
>
> So where to put the developing sources? Made the _one_ place
> and me (i hope also others) could help.
Well, ideally we push the patch upstream and then people can send
updates to this list... I think it's really close and I feel like it
can be submitted for 2.6.25.
Dan
next prev parent reply other threads:[~2007-11-07 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200711070307.09832.rootkit85@yahoo.it>
[not found] ` <20071107103445.28907089@brian.englab.brq.redhat.com>
2007-11-07 14:15 ` airo WPA Matteo Croce
2007-11-07 14:41 ` Dan Williams
2007-11-07 14:59 ` Matteo Croce
2007-11-07 15:13 ` Dan Williams [this message]
2008-02-21 0:55 ` Matteo Croce
2008-02-21 2:34 ` Dan Williams
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=1194448388.23721.0.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=achirica@users.sourceforge.net \
--cc=alessandroferrari@gmail.com \
--cc=breed@users.sourceforge.net \
--cc=castet.matthieu@free.fr \
--cc=fabrice@bellet.info \
--cc=jt@hpl.hp.com \
--cc=linux-net@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rootkit85@yahoo.it \
--cc=xschmi00@stud.feec.vutbr.cz \
/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).