{"id":1149,"date":"2010-03-05T15:30:55","date_gmt":"2010-03-05T19:30:55","guid":{"rendered":"http:\/\/www.contrapositivediary.com\/?p=1149"},"modified":"2010-03-05T15:31:59","modified_gmt":"2010-03-05T19:31:59","slug":"a-viral-ssid","status":"publish","type":"post","link":"http:\/\/www.contrapositivediary.com\/?p=1149","title":{"rendered":"A Viral SSID"},"content":{"rendered":"\n<p>First of all, you can stop worrying about me&#8211;Carol and I took an intense week-long trip to Chicago tending to family business, and I just couldn&#8217;t summon the energy to post while I was there.<\/p>\n<p>But I was reminded of an interesting thing on the trip home, while we waited at the gate for our plane at O&#8217;Hare. I opened my new laptop to check for connectivity, and in addition to the airport&#8217;s Boingo network, I saw the oft-encountered but poorly understood &#8220;Free Public Wifi&#8221; SSID. I&#8217;ve seen that SSID in airports on almost every trip I&#8217;ve taken in the last three or four years, well-aware that it&#8217;s not anything like free connectivity. I&#8217;ve always assumed that it was a virus running on somebody else&#8217;s close-by laptop, because it&#8217;s not an infrastructure node like an access point, but an ad-hoc (peer-to-peer) node instead.<\/p>\n<p>Well, it is a virus, but one of a truly fascinating sort. And that may be a little unfair. It&#8217;s not malware in the sense of adverse execution on the machine, but a consequence of some Windows foolishness in XP and (possibly) more recent versions. The &#8220;Free Public Wifi&#8221; SSID spreads virally without the help of anything except Windows itself. I never completely understood the mechanism until I looked it up yesterday. There&#8217;s a great writeup <a href=\"http:\/\/www.wlanbook.com\/free-public-wifi-ssid\/\">here<\/a>, and I&#8217;ll summarize:<\/p>\n<p>Wireless Zero Configuration (WZC) is the part of Windows that manages Wi-Fi connections. When enabled, it will do the following when the machine is booted:<\/p>\n<ol>\n<li>It looks to see if one of your preferred network SSIDs is present in the list of detected infrastructure networks, and will connect if present. Failing that,<\/li>\n<li>It attempts to connect &#8220;blind&#8221; to infrastructure networks on your preferred list that are <em>not<\/em> detected, to cover the possibility that your network&#8217;s SSID beacon is disabled. This is the Wi-Fi implementation of &#8220;security by obscurity,&#8221; and no one really uses it anymore. Having failed to connect to a hidden infrastructure node,<\/li>\n<li>WZC will look to see if one of your preferred network SSIDs is present in detected ad-hoc networks, and will connect if it finds one.<\/li>\n<li>Now the weirdness begins: If none of your preferred network SSIDs is present as an ad-hoc node, <em>and<\/em> if there is an ad-hoc SSID in your preferred networks list, <em>WZC sets your system up as an ad-hoc network with the first ad-hoc SSID it finds in your preferred list<\/em>.<\/li>\n<\/ol>\n<p>Hoo-boy. Read that again: If you&#8217;ve ever connected to an ad-hoc node and no networks in your preferred list are available, your machine becomes an ad-hoc node. This may not be the worst wireless idea ever, but it&#8217;s right up there. Basically, you&#8217;ve opened a door to your machine, and (depending on your firewall situation) if somebody connects to your laptop through the ad-hoc node that WZC has created, they can browse your shares.<\/p>\n<p>It didn&#8217;t take malware to make this happen. Windows did it all by its lonesome. Here&#8217;s a likely scenario explaining why this SSID is so commonly seen in airports:<\/p>\n<ol>\n<li>Somewhere, somewhen, there was a mesh (peer to peer) network named &#8220;Free Public WiFi.&#8221; It was probably legitimate. I don&#8217;t like mesh networks for various technical reasons, but they have their uses, and there&#8217;s nothing necessarily scurrilous about them.<\/li>\n<li>An XP user logs into this original &#8220;Free Public Wifi&#8221; network and connects to the Internet. The SSID is added to their preferred networks list as an ad-hoc node, where it remains. When finished using the mesh network, the XP user breaks the ad-hoc connection and life goes on.<\/li>\n<li>Later on, which could be months or even years, the same user (&#8220;User #1&#8221;) goes to an airport and while waiting for a plane, boots his or her laptop to do some local spreadsheet work. No connectivity is found, so Wireless Zero Configuration happily establishes an ad-hoc node called &#8220;Free Public WiFi.&#8221;<\/li>\n<li>A nearby XP user (&#8220;User #2&#8221;) boots a laptop, looking for connectivity. He or she sees &#8220;Free Public Wifi&#8221; as an available network, and (naively) clicks to connect. An ad-hoc connection is established to User #1&#8217;s laptop. Nothing happens, since neither user is connected to the Internet. However, the &#8220;Free Public Wifi&#8221; SSID is added to User #2&#8217;s preferred networks list. User #2&#8217;s plane eventually comes in, and he or she shuts down the laptop, disappointed that no free connection was found.<\/li>\n<li>Later on, User #2 is again at an airport and boots the laptop. WZC establishes an ad-hoc node, and this time, two users see the &#8220;Free Public WiFi&#8221; SSID and connect. Again, nothing either good or bad happens, but the &#8220;Free Public WiFi&#8221; ad-hoc SSID is added to the preferred networks list of both User #3 and User #4.<\/li>\n<li>User #3 and User #4 (neither of whom have any idea what&#8217;s going on) boot their laptops at other airports, or at conference centers, or some place where laptops tend to congregate. Similarly naive users connect, looking for a free Internet connection, and add &#8220;Free Public WiFi&#8221; to their preferred networks list.<\/li>\n<li>Contagion continues, as road warriors spread the SSID as explained above.<\/li>\n<\/ol>\n<p>Although malware isn&#8217;t involved, this is far from harmless, since an ad-hoc connection is a door to your machine. Your firewall will probably stop any shenanigans&#8230;if you have it working and configured correctly. Some people won&#8217;t.<\/p>\n<p>Note well that this only happens if your system has the WZC service running. If you have vendor-specific software installed to manage your wireless subsystem (as all newer Dell laptops do) this craziness won&#8217;t occur. Only if Windows and WZC are in charge of wireless are you vulnerable. The solution? Limit your connections to infrastructure networks. <a href=\"http:\/\/www.wlanbook.com\/free-public-wifi-ssid\/\">There&#8217;s a step-by-step at the end of this article<\/a>.<\/p>\n<p>Other such viral SSIDs exist; I&#8217;ve seen &#8220;hpsetup&#8221; and &#8220;default&#8221; myself, and others have been reported. Any ad-hoc network SSID can go viral with the help of Windows Wireless Zero Configuration. The &#8220;hpsetup&#8221; SSID was &#8220;contracted&#8221; from certain HP printers that connect to laptops via ad-hoc connections. I&#8217;ve only confirmed this on XP; the issue may have been resolved with Vista and 7. It&#8217;s a fascinating example of unintended consequences in system design, and should become a textbook case in CS coursework. (Why don&#8217;t I think that this will ever happen?)<\/p>\n","protected":false},"excerpt":{"rendered":"<p>First of all, you can stop worrying about me&#8211;Carol and I took an intense week-long trip to Chicago tending to family business, and I just couldn&#8217;t summon the energy to post while I was there. But I was reminded of an interesting thing on the trip home, while we waited at the gate for our [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[92,88],"class_list":["post-1149","post","type-post","status-publish","format-standard","hentry","category-noneoftheabove","tag-wi-fi","tag-windows"],"_links":{"self":[{"href":"http:\/\/www.contrapositivediary.com\/index.php?rest_route=\/wp\/v2\/posts\/1149","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.contrapositivediary.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.contrapositivediary.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.contrapositivediary.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/www.contrapositivediary.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1149"}],"version-history":[{"count":1,"href":"http:\/\/www.contrapositivediary.com\/index.php?rest_route=\/wp\/v2\/posts\/1149\/revisions"}],"predecessor-version":[{"id":1150,"href":"http:\/\/www.contrapositivediary.com\/index.php?rest_route=\/wp\/v2\/posts\/1149\/revisions\/1150"}],"wp:attachment":[{"href":"http:\/\/www.contrapositivediary.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1149"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.contrapositivediary.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1149"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.contrapositivediary.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1149"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}