|
|
|
|
|
by mikestew
3064 days ago
|
|
One popular route on a base in Iraq has been nicknamed “Base Perimeter” by the U.S. runners who regularly use it. I'm truly gobsmacked that it never occurred to anyone that this might pose a problem. Maybe not the 19 year old grunt who signed up because getting a master's in CS wasn't in his future, but c'mon, there isn't someone responsible for preventing data leakage? This is not some corner case, or some side-channel attack; Strava's whole business model rotates around "track where you've been with extreme accuracy, and let the world know about it". Otherwise I'd just keep the data locally, like I did in the old days. But even if kept locally, what happened to the worry of radio leakage? Ten years ago I worked on some stuff that might end up being used by the military, and I distinctly remember a co-worker who used to be pretty high up in the army (colonel, maybe?) pointing out that in the field things like Bluetooth, et. al., were generally frowned upon for what I thought would be obvious reasons. Perhaps with the subsequent advent of more and more devices emitting radio signals, what used to be obvious isn't so obvious anymore, so now we let military personnel run around with devices on their wrist that signal to anyone within 30m that they're there. |
|
Institutions tend to optimize so they run close to the redline, busy with a lot of stuff as it is. Adding more tasks, making them important, making everyone get educated and compliant is a huge undertaking.
Noticing and discerning what needs to be prioritized, in areas presenting such volatility and new possibilities as smartphones, apps, and data security could be daunting to do selectively.
They could ban cell phones / bt devices altogether but that will likely not go well.
As for our relationship with security, I find Richard Feynman’s experiences delightfully relevant:
http://calteches.library.caltech.edu/34/3/FeynmanLosAlamos.h...
Edit: typo