linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Cavallari <Nicolas.Cavallari@lri.fr>
To: linux-wireless <linux-wireless@vger.kernel.org>
Subject: [resent to correct list address][RFC] mac80211: tx: do not drop management frames to non-MFP STA.
Date: Fri, 15 Jun 2012 18:33:48 +0200	[thread overview]
Message-ID: <4FDB63EC.5030802@lri.fr> (raw)
In-Reply-To: <1339777624-27826-1-git-send-email-cavallar@lri.fr>

When drop_unencrypted is enabled and MFP is disabled,
non-robust management frames for not-yet associated STA are dropped.
This isn't visible as many management frames sent from the kernel
have TX_INTFL_DONT_ENCRYPT set and management frames injected
from a monitor vif have TX_CTL_INJECTED so aren't dropped.
But management frames sent from userspace via NL80211_CMD_FRAME
do not have this flag set, so are dropped.

This patch make it drop non-management frames as usual, but
only MFP STA are subject to drops when drop_unencrypted is set to 1.

This shouldn't break anything, as drop_unencrypted is only enabled
in IBSS mode when PRIVACY is requested.

Signed-off-by: Nicolas Cavallari <cavallar@lri.fr>

---

Found this while trying to handle auth frames in userspace
on a IBSS RSN network.
I'm a bit surprised that drop_unencrypted is disabled both
in AP and managed mode, but only enabled in IBSS RSN, which
does not support MFP yet, so the MFP handling is somewhat useless for now.

diff --git a/net/mac80211/tx.c b/net/mac80211/tx.c
index af25c4e..9f61e64 100644
--- a/net/mac80211/tx.c
+++ b/net/mac80211/tx.c
@@ -558,9 +558,10 @@ ieee80211_tx_h_select_key(struct ieee80211_tx_data *tx)
 	else if (tx->sdata->drop_unencrypted &&
 		 (tx->skb->protocol != tx->sdata->control_port_protocol) &&
 		 !(info->flags & IEEE80211_TX_CTL_INJECTED) &&
-		 (!ieee80211_is_robust_mgmt_frame(hdr) ||
-		  (ieee80211_is_action(hdr->frame_control) &&
-		   tx->sta && test_sta_flag(tx->sta, WLAN_STA_MFP)))) {
+		 (!ieee80211_is_mgmt(hdr->frame_control) ||
+		  (!ieee80211_is_robust_mgmt_frame(hdr) ||
+		   ieee80211_is_action(hdr->frame_control)) &&
+		   tx->sta && test_sta_flag(tx->sta, WLAN_STA_MFP))) {
 		I802_DEBUG_INC(tx->local->tx_handlers_drop_unencrypted);
 		return TX_DROP;
 	} else
-- 1.7.10.4

           reply	other threads:[~2012-06-15 16:33 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1339777624-27826-1-git-send-email-cavallar@lri.fr>]

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=4FDB63EC.5030802@lri.fr \
    --to=nicolas.cavallari@lri.fr \
    --cc=linux-wireless@vger.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).