4 ms·
Before reading, I guessed that "millions of phones" meant millions of Android phones. Because if this was happening on iPhones, that would merit mention in the
by funkah 15y ago
Before reading, I guessed that "millions of phones" meant millions of Android phones. Because if this was happening on iPhones, that would merit mention in the headline. Funny how that works.
- roflharrison 15y ago>Funny how that works How what works? I see just as many "Android phones do this naughtiness" headlines as I see "iPhones allow these shenanigans" headlines. The fact that is isn't mentioned in the header lends more credence to the author (and article).
- dignan 15y agoFTA: "Eckhart said he chose the HTC phone purely for demonstration purposes. Blackberrys, other Android-powered handsets, and smartphones from Nokia contain the same snooping software, he claims." It's not "Android" phones alone, it seems like everything but iPhones and Windows phones. Thus, the title is accurate.
- smokinn 15y agoAnd you guessed wrong. It says iphones and blackberrys are equally affected.
- artursapek 15y agoBlackberries possibly, I saw no mention of iOS devices.
- gcb 15y agoIos also collects all that. It's just more difficult to see inside a safe. Remember the js code that showed all the places the phone have been using a mere phone backup data? ios is already worse then all of this
- masklinn 15y ago> Ios also collects all that. Do you have the slightest evidence for your claim? > It's just more difficult to see inside a safe. Anything can be seen on a jailbroken iphone. > Remember the js code that showed all the places the phone have been using a mere phone backup data? This was (explained as) a location cache the developer forgot to clean (most phones will cache the last few locations so it does not have to boot the location circuitry if an application only needing a very rough location estimate needs a fix) which mistakenly existed in a backuped location (note that unless users sent them, those backups never left their machine). And the issue was fixed in the next update (both the backuping and the too-greedy cache). > ios is already worse then all of this I'll go with no until you provide evidence.
- artursapek 15y agoYou made me wonder- is jailbreaking an iPhone the equivalent of rooting an Android phone? It's just about becoming the root user in the Unix system right? I've never played with either.
- gcb 15y agorooting both is the same conceptually, your guess is right. Then there's also the privilege of the apps. which i have no idea how it works on ios.
- gcb 15y agoyou assume too much of rooting. getting root access is NOT the same as looking at source code. and i don't know anyone reversed the code for IOS besides the small activation parts. loggers could pretty much do nothing if device is not stock. what else could be have 'too greedy logging' 'by mistake'? you and me will never know. may be nothing.
- masklinn 15y ago> you assume too much of rooting. No. > getting root access is NOT the same as looking at source code. Er... duh? That doesn't matter, the kind of issues we're talking about here is usually discovered via blackbox testing (not whitebox), by tracing syscalls or core API calls (no need for source access for that) as well as network communications (no need for sources either). > loggers could pretty much do nothing if device is not stock. And the vast majority of devices are stock. > what else could be have 'too greedy logging' 'by mistake'? you and me will never know. Logging has to go somewhere, logging that goes nowhere is pointless. As soon as logging goes somewhere, it can be seen and traced.
- masklinn 15y ago> It says iphones and blackberrys are equally affected. No, it says Blackberries and Nokia phones are equally affected. The application requires 1. carrier-custom ROMs and 2. very low level access to the OS. Both are things iOS does not provide, Apple does not allow carriers to tinker with iOS images and does not allow low-level OS access (unless you jailbreak).