From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: John Linville <linville@tuxdriver.com>, netdev@vger.kernel.org
Subject: Re: [PATCH] ieee80211: quiet TKIP and CCMP replay messages for identical TSCs
Date: Tue, 26 Sep 2006 09:44:04 +0200 [thread overview]
Message-ID: <1159256644.2782.3.camel@ux156> (raw)
In-Reply-To: <4517FA78.mailH4P11L3ZE@lwfinger.net>
On Mon, 2006-09-25 at 10:49 -0500, Larry Finger wrote:
> When using TKIP and CCMP for wireless encryption with ieee80211, the logs get filled with useless
> replay messages where the previous and received TSC are identical. This change deletes
> the log message for this case, but still prints the message when there are major differences
> in the TSC's.
Hey, that seems like a good idea to get rid of the messages no one wants
to see (in the retransmit case) but still warn if someone is really
messing with it.
Acked-by: Johannes Berg <johannes@sipsolutions.net>
johannes
next prev parent reply other threads:[~2006-09-26 7:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 15:49 [PATCH] ieee80211: quiet TKIP and CCMP replay messages for identical TSCs Larry Finger
2006-09-26 7:44 ` Johannes Berg [this message]
2006-09-28 16:02 ` Jouni Malinen
2006-09-29 7:41 ` Johannes Berg
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=1159256644.2782.3.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=linville@tuxdriver.com \
--cc=netdev@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).