Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751977AbXA3W63 (ORCPT ); Tue, 30 Jan 2007 17:58:29 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751972AbXA3W63 (ORCPT ); Tue, 30 Jan 2007 17:58:29 -0500 Received: from dhost002-68.dex002.intermedia.net ([64.78.20.34]:24774 "EHLO DHOST002-68.dex002.intermedia.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751943AbXA3W62 (ORCPT ); Tue, 30 Jan 2007 17:58:28 -0500 X-Greylist: delayed 305 seconds by postgrey-1.27 at vger.kernel.org; Tue, 30 Jan 2007 17:58:28 EST From: "Jouni Malinen" Date: Tue, 30 Jan 2007 14:56:41 -0800 To: Larry Finger Cc: Dan Williams , Johannes Berg , netdev , LKML Subject: Re: Hidden SSID's Message-ID: <20070130225641.GH32304@instant802.com> References: <45BACB71.2080107@lwfinger.net> <1169899689.25670.3.camel@localhost.localdomain> <1170019717.30318.0.camel@johannes.berg> <1170075611.2895.2.camel@localhost.localdomain> <20070130030911.GA6637@jm.kir.nu> <1170128208.3448.6.camel@localhost.localdomain> <45BECF04.3070904@lwfinger.net> <20070130050841.GC6637@jm.kir.nu> <45BEEEED.9010702@lwfinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45BEEEED.9010702@lwfinger.net> User-Agent: Mutt/1.4.2.1i X-OriginalArrivalTime: 30 Jan 2007 22:56:42.0477 (UTC) FILETIME=[E89479D0:01C744C1] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1540 Lines: 28 On Tue, Jan 30, 2007 at 01:08:29AM -0600, Larry Finger wrote: > Any AP with a hidden SSID will only respond to probe requests that specify its SSID, and will ignore > any other probes. In addition, the response will have an empty SSID field. These responses are the > only ones in which a substitution would occur. These are the same responses where the current code > sends back the "" pseudo-SSID. My change would put the correct one there. Is the SSID from the probe response really used here? Your patch did not look like that.. The SSID from the last scan request command may not be the one that triggered the last scan (e.g., one could request a new scan without specifying an SSID). > We aren't guessing. The response frame with the empty SSID field must have come from the AP with the > SSID we want. Filling in the expected value is just making it easier for the user-space tools. I don't see how the proposed patch would be using the correct SSID value in all cases. Especially cases where there are multiple APs using hidden SSIDs, but with different real SSID values and cases where multiple scan requests are being processed would be likely to leave windows open for reporting incorrect SSID. -- Jouni Malinen PGP id EFC895FA - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/