Skip to main content

Would You Give up Your Credit Card Number for an Hour of Free Wireless?

  • Cool: The City of Minneapolis has city-wide WiFi.
  • Cooler: The City of Minneapolis is offering free WiFi hotspots at selected spots in the city.
  • Coolest: It works.
  • Uncool: To use the free hot spots, you have to surrender a credit card number.

Would you give up a CC number just to get free WiFi?

  • This probably isn’t any worse that handing your card to a waiter at a restaurant.
  • I don’t know what else one could request that would provide a bit of verification of a users identity. A drivers license?
  • One could simply decide to not care who uses the free hotspots. Our big brothers at the University don’t. They offer free guest wireless with only an e-mail address. For them, is an e-mail address.
  • It’s entirely possible that the vendor that built and owns the the network is PCI-DSS SAQ-whatever compliant.

I don’t think that I’d give up a card number just to get free WiFi.

I will assert though, that most people will.


  1. As long as the prefix is valid and it passes the Luhn check, right? woot! :D

  2. It's not justifiable given the various wi-fi hotspots readily available everywhere.


Post a Comment

Popular posts from this blog

Cargo Cult System Administration

Cargo Cult: …imitate the superficial exterior of a process or system without having any understanding of the underlying substance --Wikipedia During and after WWII, some native south pacific islanders erroneously associated the presence of war related technology with the delivery of highly desirable cargo. When the war ended and the cargo stopped showing up, they built crude facsimiles of runways, control towers, and airplanes in the belief that the presence of war technology caused the delivery of desirable cargo. From our point of view, it looks pretty amusing to see people build fake airplanes, runways and control towers  and wait for cargo to fall from the sky.
The question is, how amusing are we?We have cargo cult science[1], cargo cult management[2], cargo cult programming[3], how about cargo cult system management?Here’s some common system administration failures that might be ‘cargo cult’:
Failing to understand the difference between necessary and sufficient. A daily backup …

Ad-Hoc Versus Structured System Management

Structured system management is a concept that covers the fundamentals of building, securing, deploying, monitoring, logging, alerting, and documenting networks, servers and applications. Structured system management implies that you have those fundamentals in place, you execute them consistently, and you know all cases where you are inconsistent. The converse of structured system management is what I call ad hoc system management, where every system has it own plan, undocumented and inconsistent, and you don't know how inconsistent they are, because you've never looked.

In previous posts (here and here) I implied that structured system management was an integral part of improving system availability. Having inherited several platforms that had, at best, ad hoc system management, and having moved the platforms to something resembling structured system management, I've concluded that implementing basic structure around system management will be the best and fastest path to…

The Cloud – Provider Failure Modes

In The Cloud - Outsourcing Moved up the Stack[1] I compared the outsourcing that we do routinely (wide area networks) with the outsourcing of the higher layers of the application stack (processor, memory, storage). Conceptually they are similar:In both cases you’ve entrusted your bits to someone else, you’ve shared physical and logical resources with others, you’ve disassociated physical devices (circuits or servers) from logical devices (virtual circuits, virtual severs), and in exchange for what is hopefully better, faster, cheaper service, you give up visibility, manageability and control to a provider. There are differences though. In the case of networking, your cloud provider is only entrusted with your bits for the time it takes for those bits to cross the providers network, and the loss of a few bits is not catastrophic. For providers of higher layer services, the bits are entrusted to the provider for the life of the bits, and the loss of a few bits is a major problem. These …