Another article on this, I agree with Dan's assessment - http://arstechnica.com/securit...
"Never attribute to malice that which can be attributed to stupidity."
My guess, after years of working with Samsung's poor-quality platform software and multiple runins with their utterly piss-poor configuration management processes (as in, the Korean divisions at Samsung Mobile don't seem to have any, as evidenced by numerous situations during the Superbrick fiasco):
Samsung probably put this into the RIL library to facilitate modem debugging. e.g. the modem can read/write to
Keep in mind that, based on the reverse engineering effort, Samsung *intended* this feature to only access files within
So at some point, Samsung probably removed the corresponding components on the baseband firmware side (no one has yet to confirm anything on the modem side that sends these commands, nor has anyone caught any of these commands being issued - the behavior of the library was verified by injecting extra commands with a kernel patch in the driver between the modem and the library), but someone forgot to remove them from the RIL library on the applications processor side. Forgetting to remove dead code and/or leaving epic security holes in place (remember that in late 2012, someone realized that Samsung left a world readable/writable device node that effectively mapped all system memory to that device file - allowing anyone to read or write any part of memory. For more, do a Google search for "exynos-abuse" ) is pretty typical for Samsung.
As to my experience here - I was one of the Cyanogenmod maintainers for the Exynos 4210 (I9100, I777, N7000) handset family, and also did some work on 4412 devices (primarily the Note 10.1 - GT-N8013) throughout 2012 and the first half of 2013. I'm 90% retired from working with Haxxinos these days and was (along with the majority of the rest of the Exynos maintainers) one of the people who left the project to start Omni after the Focal relicensing attempt fiasco.
An interesting question is - what architecture is the XMM626x's baseband processor? Is it custom or an ARM variant making it easier to analyze the baseband firmware itself? More than two years of working with that family of devices and I never personally looked in detail at what was running on the baseband side.
In a particular case like this, it may be possible for much of the transport work to be done by volunteers from the local ham community.
W2CXM's Force12 antenna was entirely put up by volunteers. This isn't exactly a small antenna - http://www.qsl.net/w2cxm/pics....
Yup. Here it's perfectly legal if you're informed. Any time I log into a machine at work I get a banner that my employer reserves the right to monitor anything I do with their network.
Because it's a shitty law that has too many dangerous drawbacks, and they already have a better solution (IMEI/ESN blacklisting) in place.
Yup. There are plenty of "opt-in" solutions to mobile device management right now.
Thing is, I know of none that can completely brick a device after a wipe, and I have grave concerns over such a capability because of the damage it does if it accidentally goes off. If it can't completely brick a device, at best it can protect your data but not the smartphone itself.
The thing is, there are already solutions for smartphone theft. A smartphone, to be fully useful, needs service from a wireless carrier. To get service, a device must report its IMEI or ESN. IMEI/ESN blacklists already exist and are in use today.
"Hacking was encouraged—users and developers were told they could root the console without voiding its warranty."
Problem was that it came out early that this wasn't a particularly "hackable" console due to some design flaws.
1) If you're doing platform-level hacking, Tegra3 is not a pleasant chipset to work with
2) It had some issues as I understand it with fastboot mode (I don't recall the exact details, but it either was extremely difficult to enter or simply didn't exist) - as a result it was very easy to brick the Ouya. The news of this drove away quite a lot of the potential enthusiast/power users.
Yes. Maps on Glass is already far less distracting than a windshield-mounted GPS for example, and there are also speedometer/OBD apps for Glass people are working on.
Yup. In which case, if you ban Glass, you must also completely ban all windshield-mounted GPS units.
AT&T already has an IMEI blacklist. I believe they are exchanging data internationally already too. (The GSMA has an international shared blacklist - http://www.gsma.com/technicalp... )
Yup. The carriers already HAVE an effective killswitch: A database of IMEIs reported as stolen which the network can (and DOES) blacklist. (I know for a fact that AT&T does blacklisting as Samsung devices change to a "default" test IMEI if their EFS partition is corrupted - this IMEI is blacklisted by AT&T.)
If users want something more than that they have plenty of options available to them at their own risk.
So what if someone puts a URL for a cheat site in a forum comment somewhere, disguised as something else?
Was the driver a smoker?
The same people who buy crap from Micromax.
"“Once a year they pick cities like Denver or London and rescan them and they get it into their database – how often Google buys those images and updates its maps, is up to them.”
I'm surprised that Google is still buying DigitalGlobe imagery for the continental USA, ESPECIALLY for major metropolitan areas.
Most states have state-level orthoimagery collection programs, and as a result, there is high-quality aerial imagery significantly exceeding these satellites in quality over most of the USA, especially in metropolitan areas.
For example, New York State has 2 foot (24 inch) resolution across the entire state (only slightly worse than DigitalGlobe's best quality available), and over much of the state has 1 foot (12 inch) and even 0.5 foot (6 inch) resolution, the latter of which is better than what DG offers government customers. This data is under similar extremely permissive licensing to most other government GIS data such as TIGER. (Anyone can download NYGIS orthoimagery, and this same imagery is what Google uses for Maps/Earth for "satellite" which is really "aerial")
Pennsylvania has similar quality statewide imagery. Same for New Jersey (1 foot in the case of NJ).