linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benoit PAPILLAULT <benoit.papillault@free.fr>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Jouni Malinen <j@w1.fi>
Subject: Re: [PATCH 1/2] mac80211: Ignore replay for IBSS interfaces
Date: Mon, 15 Feb 2010 23:41:05 +0100	[thread overview]
Message-ID: <4B79CD81.3090300@free.fr> (raw)
In-Reply-To: <1266225762.3758.1.camel@jlt3.sipsolutions.net>

Johannes Berg a écrit :
> On Mon, 2010-02-15 at 00:32 +0100, Benoit Papillault wrote:
>   
>> Using WPA-NONE, the same key is used on multiple stations. As such,
>> with
>> at least 3 nodes, a node will receive frames from the other 2 nodes
>> and
>> frames from one of those nodes will be ignored since they are being
>> detected as replayed.
>>
>> Note: WPA-NONE is not specified in 802.11i. Instead WPA2 should be
>> used,
>> but it is not currently implemented.
>>
>> Signed-off-by: Benoit Papillault <benoit.papillault@free.fr>
>> ---
>>  net/mac80211/tkip.c |    6 +++++-
>>  net/mac80211/wpa.c  |   10 +++++++---
>>  2 files changed, 12 insertions(+), 4 deletions(-)
>>
>> diff --git a/net/mac80211/tkip.c b/net/mac80211/tkip.c
>> index 7ef491e..f7e0062 100644
>> --- a/net/mac80211/tkip.c
>> +++ b/net/mac80211/tkip.c
>> @@ -234,6 +234,7 @@ int ieee80211_tkip_decrypt_data(struct
>> crypto_blkcipher *tfm,
>>  	u8 rc4key[16], keyid, *pos = payload;
>>  	int res;
>>  	const u8 *tk = &key->conf.key[NL80211_TKIP_DATA_OFFSET_ENCR_KEY];
>> +	bool tkip_decrypt_replay = 0;
>>  
>>  	if (payload_len < 12)
>>  		return -1;
>> @@ -271,7 +272,7 @@ int ieee80211_tkip_decrypt_data(struct
>> crypto_blkcipher *tfm,
>>  		       iv32, iv16, key->u.tkip.rx[queue].iv32,
>>  		       key->u.tkip.rx[queue].iv16);
>>  #endif
>> -		return TKIP_DECRYPT_REPLAY;
>> +		tkip_decrypt_replay = 1;
>>  	}
>>  
>>  	if (only_iv) {
>> @@ -338,5 +339,8 @@ int ieee80211_tkip_decrypt_data(struct
>> crypto_blkcipher *tfm,
>>  		*out_iv16 = iv16;
>>  	}
>>  
>> +	if (tkip_decrypt_replay)
>> +		return TKIP_DECRYPT_REPLAY;
>> +
>>  	return res;
>>  }
>> diff --git a/net/mac80211/wpa.c b/net/mac80211/wpa.c
>> index f4971cd..da1186d 100644
>> --- a/net/mac80211/wpa.c
>> +++ b/net/mac80211/wpa.c
>> @@ -242,7 +242,9 @@ ieee80211_crypto_tkip_decrypt(struct
>> ieee80211_rx_data *rx)
>>  					  hdr->addr1, hwaccel, rx->queue,
>>  					  &rx->tkip_iv32,
>>  					  &rx->tkip_iv16);
>> -	if (res != TKIP_DECRYPT_OK || wpa_test)
>> +	if ((res != TKIP_DECRYPT_OK || wpa_test) &&
>> +	    !(res == TKIP_DECRYPT_REPLAY &&
>> +	      rx->sdata->vif.type != NL80211_IFTYPE_ADHOC))
>>  		return RX_DROP_UNUSABLE;
>>     
>
> NACK. This will clearly _break_ any proper RSN implementation. WPA-NONE
> is the non-standard thing here, so requiring that somebody wanting to
> implement proper RSN fix this doesn't seem right to me. And RSN
> shouldn't actually be hard to implement with the events that we have now
> -- it might just be a userspace thing.
>
> johannes
>   
Right. This patch disable replay protection. RSN is indeed the correct 
solution, but it's out of reach for me (no time, no skills). As such, I 
thought that WPA-NONE could be useful in the interim.

Jouni : I would appreciate your input here. What's the status of IBSS 
RSN? How much time/skills would be required to implement it?

Regards,
Benoit



  reply	other threads:[~2010-02-15 22:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-14 23:32 [PATCH 1/2] mac80211: Ignore replay for IBSS interfaces Benoit Papillault
2010-02-14 23:32 ` [PATCH 2/2] mac80211: Fix WPA-NONE for RX unicast frames Benoit Papillault
2010-02-15  9:24   ` Johannes Berg
2010-02-15  9:22 ` [PATCH 1/2] mac80211: Ignore replay for IBSS interfaces Johannes Berg
2010-02-15 22:41   ` Benoit PAPILLAULT [this message]
2010-02-16  7:46     ` Jouni Malinen
2010-02-16 20:34       ` Benoit PAPILLAULT

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=4B79CD81.3090300@free.fr \
    --to=benoit.papillault@free.fr \
    --cc=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --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).