netdev - Re: [Bugme-new] [Bug 8053] New: net/ieee80211/ieee80211_crypt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <45E0FAA4.6000408@lwfinger.net>
Date:	Sat, 24 Feb 2007 20:55:32 -0600
From:	Larry Finger <larry.finger@...inger.net>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	netdev@...r.kernel.org,
	"John W. Linville" <linville@...driver.com>,
	"bugme-daemon@...nel-bugs.osdl.org" 
	<bugme-daemon@...zilla.kernel.org>, ast@...dv.de, stable@...nel.org
Subject: Re: [Bugme-new] [Bug 8053] New: net/ieee80211/ieee80211_crypt_tkip.c
 spams kernel message buffer

Andrew Morton wrote:
> On Wed, 21 Feb 2007 16:57:59 -0800
> bugme-daemon@...zilla.kernel.org wrote:
> 
>> http://bugzilla.kernel.org/show_bug.cgi?id=8053
>>
>>            Summary: net/ieee80211/ieee80211_crypt_tkip.c spams kernel
>>                     message buffer
>>     Kernel Version: 2.6.20.1
>>             Status: NEW
>>           Severity: high
>>              Owner: networking_wireless@...nel-bugs.osdl.org
>>          Submitter: ast@...dv.de
>>
>>
>> As sent to lkml and netdev on 2007/02/07 without any reply:
>>
>> net/ieee80211/ieee80211_crypt_tkip.c outputs tons of these which didn't
>> happen with 2.6.18.2 (only one or two of these after enabling the
>> ipw2200 with the kill switch):
>>
>> TKIP: replay detected: STA=00:0e:2e:94:84:c3 previous TSC 020000000000
>> received TSC 00000002e560
>> printk: 19 messages suppressed.
>> TKIP: replay detected: STA=00:0e:2e:94:84:c3 previous TSC 020000000000
>> received TSC 00000002e574
>> printk: 19 messages suppressed.
>> TKIP: replay detected: STA=00:0e:2e:94:84:c3 previous TSC 020000000000
>> received TSC 00000002e588
>> printk: 18 messages suppressed.
>> TKIP: replay detected: STA=00:0e:2e:94:84:c3 previous TSC 020000000000
>> received TSC 00000002e59b
>> printk: 19 messages suppressed.
>> TKIP: replay detected: STA=00:0e:2e:94:84:c3 previous TSC 020000000000
>> received TSC 00000002e5af
>> printk: 19 messages suppressed.
>> TKIP: replay detected: STA=00:0e:2e:94:84:c3 previous TSC 020000000000
>> received TSC 00000002e5c3
>> printk: 19 messages suppressed.
>> TKIP: replay detected: STA=00:0e:2e:94:84:c3 previous TSC 020000000000
>> received TSC 00000002e5d7
>> printk: 19 messages suppressed.
>> TKIP: replay detected: STA=00:0e:2e:94:84:c3 previous TSC 020000000000
>> received TSC 00000002e5eb
>> printk: 19 messages suppressed.
>> TKIP: replay detected: STA=00:0e:2e:94:84:c3 previous TSC 020000000000
>> received TSC 00000002e5ff
>> printk: 16 messages suppressed.
>> TKIP: replay detected: STA=00:0e:2e:94:84:c3 previous TSC 020000000000
>> received TSC 00000002e612
>> printk: 17 messages suppressed.
>> TKIP: replay detected: STA=00:0e:2e:94:84:c3 previous TSC 020000000000
>> received TSC 00000002e626
>>
>> Note that the AP in question is a LCS-WA5-40 running in WPA/WPA2 mixed mode and
>> that the client in uses:
>>
>> proto=RSN
>> pairwise=CCMP
>> group=TKIP
>>
> 
> How rude.  Can we please get that message killed in both 2.6.21 and
> 2.6.20.x?

With the previous TSC having that strange value (020000000000), there must be some sort of driver
and/or AP error. With the possible exception of the situation where the "previous" and "received"
TSC are the same indicating a retransmit, I feel such messages are of value and do not support
killing them.

Larry


-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html