[86878] in North American Network Operators' Group
Wifi Security
daemon@ATHENA.MIT.EDU (Ross Hosman)
Mon Nov 21 09:41:22 2005
Date: Mon, 21 Nov 2005 08:42:42 -0600
From: "Ross Hosman" <rhosman@corp.hometel.com>
To: <nanog@nanog.org>
Errors-To: owner-nanog@merit.edu
This is a multi-part message in MIME format.
------_=_NextPart_001_01C5EEA9.D607F3BA
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
So my question is pretty simple. You have all these major companies such
as google/earthlink/sprint/etc. building wifi networks. Lets say I want
to collect peoples information so I setup an AP with the same ssid as
google's ap so people connect to it and I log all of their traffic. Most
people won't check beyond the ssid to look at the mac address but even
that could be spoofed. Is there anyway to verify a certain ap beyond
mac/ssid, will there be in the future? How do these companies plan to
mitigate this threat or are they just going to hope consumers are smart
enough to figure it out?
Ross Hosman
Network/Systems Administrator
E: rhosman@corp.hometel.com
P: 618-644-2111 x 238
C: 314-898-3381
Y!: rosshosman
------_=_NextPart_001_01C5EEA9.D607F3BA
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7226.0">
<TITLE>Wifi Security</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">So my =
question is pretty simple.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">You have</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">all these major companies =
such as google/earthlink/sprint/etc.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">building wifi networks. Lets say I want to collect =
peoples information so I setup an</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">AP</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial"> with the same ssid as =
google</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">’</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">s ap so people connect to it and I log all of their =
traffic. Most</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">people =
won</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Arial">’</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">t check beyond the ssid to look at the mac address but =
even that could be spoofed. Is there anyway to verify =
a</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT =
SIZE=3D2 FACE=3D"Arial">certain ap beyond mac/ssid, will there be in the =
future? How do these companies plan to mitigate this threat or are they =
just going to hope consumers are smart enough to figure it =
out?</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"></SPAN><A NAME=3D""><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Ross =
Hosman</FONT></SPAN></A></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Network/Systems Administrator<BR>
E: rhosman@corp.hometel.com</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">P: =
618-644-2111 x 238</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">C: =
314-898-3381</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Y!: =
rosshosman</FONT></SPAN></P>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"></SPAN></P>
</BODY>
</HTML>
------_=_NextPart_001_01C5EEA9.D607F3BA--
