From owner-freebsd-bugs@FreeBSD.ORG Mon May 6 22:00:01 2013 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9EAD34E0 for ; Mon, 6 May 2013 22:00:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 856D9A44 for ; Mon, 6 May 2013 22:00:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r46M013M053346 for ; Mon, 6 May 2013 22:00:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r46M01Tx053345; Mon, 6 May 2013 22:00:01 GMT (envelope-from gnats) Resent-Date: Mon, 6 May 2013 22:00:01 GMT Resent-Message-Id: <201305062200.r46M01Tx053345@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, adrian chadd Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 7A9E2E2D for ; Mon, 6 May 2013 21:50:58 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from oldred.FreeBSD.org (oldred.freebsd.org [8.8.178.121]) by mx1.freebsd.org (Postfix) with ESMTP id 5383E988 for ; Mon, 6 May 2013 21:50:58 +0000 (UTC) Received: from oldred.FreeBSD.org ([127.0.1.6]) by oldred.FreeBSD.org (8.14.5/8.14.5) with ESMTP id r46LowKo039412 for ; Mon, 6 May 2013 21:50:58 GMT (envelope-from nobody@oldred.FreeBSD.org) Received: (from nobody@localhost) by oldred.FreeBSD.org (8.14.5/8.14.5/Submit) id r46LowJc039350; Mon, 6 May 2013 21:50:58 GMT (envelope-from nobody) Message-Id: <201305062150.r46LowJc039350@oldred.FreeBSD.org> Date: Mon, 6 May 2013 21:50:58 GMT From: adrian chadd To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Subject: misc/178378: [net80211] crypto state isn't reset during a reassociation X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 May 2013 22:00:01 -0000 >Number: 178378 >Category: misc >Synopsis: [net80211] crypto state isn't reset during a reassociation >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon May 06 22:00:01 UTC 2013 >Closed-Date: >Last-Modified: >Originator: adrian chadd >Release: >Organization: >Environment: >Description: When a station reassociates, the crypto state (eg CCMP RSC/TSC counters) may not be reset "right". >How-To-Repeat: What I see: * doing lots of UDP TX from FreeBSD STA -> FreeBSD AP; * the station reassociates; * .. lots of CCMP replay attack complaints on the AP side. >Fix: >Release-Note: >Audit-Trail: >Unformatted: