All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Sujith Manoharan <sujith@msujith.org>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] ath10k: Fix shared WEP
Date: Wed, 26 Nov 2014 08:38:10 +0200	[thread overview]
Message-ID: <87lhmyxy99.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1416896220-29691-1-git-send-email-sujith@msujith.org> (Sujith Manoharan's message of "Tue, 25 Nov 2014 11:46:58 +0530")

Sujith Manoharan <sujith@msujith.org> writes:

> From: Sujith Manoharan <c_manoha@qca.qualcomm.com>
>
> When static keys are used in shared WEP, when a
> station is associated, message 3 is sent with an
> encrypted payload. But, for subsequent
> authentications that are triggered without a
> deauth, the auth frame is decrypted by the HW.
>
> To handle this, check if the WEP keys have already
> been set for the peer and if so, mark the
> frame as decrypted. This scenario can happen
> when a station changes its default TX key and initiates
> a new authentication sequence.
>
> Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>

Thanks, all three applied.

-- 
Kalle Valo

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Sujith Manoharan <sujith@msujith.org>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH v2 1/3] ath10k: Fix shared WEP
Date: Wed, 26 Nov 2014 08:38:10 +0200	[thread overview]
Message-ID: <87lhmyxy99.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1416896220-29691-1-git-send-email-sujith@msujith.org> (Sujith Manoharan's message of "Tue, 25 Nov 2014 11:46:58 +0530")

Sujith Manoharan <sujith@msujith.org> writes:

> From: Sujith Manoharan <c_manoha@qca.qualcomm.com>
>
> When static keys are used in shared WEP, when a
> station is associated, message 3 is sent with an
> encrypted payload. But, for subsequent
> authentications that are triggered without a
> deauth, the auth frame is decrypted by the HW.
>
> To handle this, check if the WEP keys have already
> been set for the peer and if so, mark the
> frame as decrypted. This scenario can happen
> when a station changes its default TX key and initiates
> a new authentication sequence.
>
> Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>

Thanks, all three applied.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  parent reply	other threads:[~2014-11-26  6:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25  6:16 [PATCH v2 1/3] ath10k: Fix shared WEP Sujith Manoharan
2014-11-25  6:16 ` Sujith Manoharan
2014-11-25  6:16 ` [PATCH v2 2/3] ath10k: Fix locking for WEP keys Sujith Manoharan
2014-11-25  6:16   ` Sujith Manoharan
2014-11-25  6:17 ` [PATCH v2 3/3] ath10k: Fix bug reported by lockdep Sujith Manoharan
2014-11-25  6:17   ` Sujith Manoharan
2014-11-26  6:38 ` Kalle Valo [this message]
2014-11-26  6:38   ` [PATCH v2 1/3] ath10k: Fix shared WEP Kalle Valo

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=87lhmyxy99.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sujith@msujith.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.