From owner-freebsd-bugs@FreeBSD.ORG Tue Apr 18 17:20:24 2006 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8151B16A401 for ; Tue, 18 Apr 2006 17:20:24 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E54A643D6E for ; Tue, 18 Apr 2006 17:20:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k3IHKJKG065001 for ; Tue, 18 Apr 2006 17:20:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k3IHKJPE064999; Tue, 18 Apr 2006 17:20:19 GMT (envelope-from gnats) Date: Tue, 18 Apr 2006 17:20:19 GMT Message-Id: <200604181720.k3IHKJPE064999@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Christopher Chin Cc: Subject: Re: bin/95956: 128-bit X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Christopher Chin List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 17:20:24 -0000 The following reply was made to PR bin/95956; it has been noted by GNATS. From: Christopher Chin To: bug-followup@freebsd.org Cc: Subject: Re: bin/95956: 128-bit Date: Tue, 18 Apr 2006 10:11:28 -0700 (PDT) On Mon, 17 Apr 2006 (19:50 -0000), Mark Linimon wrote: > > Synopsis: 128-bit > > State-Changed-From-To: open->closed > State-Changed-By: linimon > State-Changed-When: Mon Apr 17 19:49:11 UTC 2006 > State-Changed-Why: > The 108-bit key is understood to be the correct behavior. Hmmm... turns out that a better answer would have been for me to (re-)read the 6-0 Release Notes... particularly section 2.2.2.2. Network Interface Support. Apparently: "Note in particular that WEP now requires the wlan_wep module to be loaded (or compiled) into the kernel." All fine and good... but I'd be surprised if others don't trip on this as well when 6.x gets more usage. Oh... Sorry about the lame subject line. I hit the submit button before going back and "fixing" the Subject. Thanks, - Christopher ======================