From: drago01 <drago01@gmail.com>
To: "Emmanuel Grumbach" <egrumbach@gmail.com>
Cc: "Volker Braun" <vbraun@physics.upenn.edu>,
"Tomas Winkler" <tomasw@gmail.com>,
"Linux Wireless" <linux-wireless@vger.kernel.org>
Subject: Re: dynamic wep with mulitple keys
Date: Mon, 12 May 2008 13:47:59 +0200 [thread overview]
Message-ID: <f6ca9fed0805120447wf6c1c38mea24ba587dc834d4@mail.gmail.com> (raw)
In-Reply-To: <8704f27d0805060514i59db36f0t9801fab7543b8655@mail.gmail.com>
On Tue, May 6, 2008 at 2:14 PM, Emmanuel Grumbach <egrumbach@gmail.com> wrote:
>
> On Tue, May 6, 2008 at 3:10 PM, drago01 <drago01@gmail.com> wrote:
> >
> > On Tue, May 6, 2008 at 9:32 AM, Emmanuel Grumbach <egrumbach@gmail.com> wrote:
> > >
> > > On Tue, May 6, 2008 at 10:22 AM, drago01 <drago01@gmail.com> wrote:
> > > > On Tue, May 6, 2008 at 8:46 AM, Emmanuel Grumbach <egrumbach@gmail.com> wrote:
> > > > > > I just tried compat-wireless-2008-05-05, which does contain
> > > > > > 03dcb07e74a62eec2badb9f6a091790c484f4a6c. No difference:
> > > > > >
> > > > >
> > > > > Thanks for trying this.
> > > > > Can you try to load the module with swcrypto=1 and try again ?
> > > > > This disables the HW encryption acceleration. Trying this will allow
> > > > > to make 100% sure that the bug is in iwlwifi. The bug is likely to be
> > > > > there, but I think it is worth to make this 100% sure.
> > > >
> > > > Well it happens for me with iwl3945 which uses swcrypto by default see:
> > > >
> > > > http://marc.info/?l=linux-wireless&m=120699235803881&w=2
> > > >
> > >
> > > Actually, I made quite a lot of changes in security in iwl4965 that
> > > are not in iwl3945 so I think it is worth trying with iwl4965 in SW.
> > > The security code is not the same between 3945 and 4965
> >
> > OK, are you planning to port this changes/fixes to 3945 ?
> >
>
> Well... Low priority...
This changes fix an important bug that otherwise make the driver
useless in some configurations.
So I think it should be backported to 3945 (even when development is
focused on newer hardware)
next prev parent reply other threads:[~2008-05-12 11:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 16:52 dynamic wep with mulitple keys Volker Braun
2008-04-23 17:15 ` Tomas Winkler
2008-05-05 14:36 ` Emmanuel Grumbach
[not found] ` <8704f27d0805050735s647ac4aaq469630bde6bc341e@mail.gmail.com>
2008-05-05 15:58 ` Volker Braun
2008-05-06 6:46 ` Emmanuel Grumbach
2008-05-06 7:22 ` drago01
2008-05-06 7:32 ` Emmanuel Grumbach
2008-05-06 12:10 ` drago01
2008-05-06 12:14 ` Emmanuel Grumbach
2008-05-12 11:47 ` drago01 [this message]
2008-05-12 12:07 ` Tomas Winkler
2008-05-12 12:10 ` drago01
2008-05-12 12:22 ` Tomas Winkler
2008-05-12 12:38 ` drago01
2008-05-13 9:24 ` Johannes Berg
2008-05-13 9:44 ` drago01
2008-05-13 10:07 ` Johannes Berg
2008-05-13 10:13 ` drago01
2008-05-13 10:18 ` Johannes Berg
2008-05-08 18:31 ` Volker Braun
2008-05-08 18:49 ` Emmanuel Grumbach
2008-05-12 9:13 ` Emmanuel Grumbach
2008-05-12 11:55 ` Emmanuel Grumbach
2008-05-13 13:53 ` Volker Braun
2008-05-13 14:06 ` Emmanuel Grumbach
2008-05-13 14:15 ` Tomas Winkler
2008-05-05 16:04 ` Emmanuel Grumbach
-- strict thread matches above, loose matches on Subject: below --
2008-03-31 19:37 drago01
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=f6ca9fed0805120447wf6c1c38mea24ba587dc834d4@mail.gmail.com \
--to=drago01@gmail.com \
--cc=egrumbach@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=tomasw@gmail.com \
--cc=vbraun@physics.upenn.edu \
/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