Live data from Hacker News

Major Android Bug Is a Privacy Disaster (CVE-2014-6041)

community.rapid7.com

51–60 of 232 posts

Re: Major Android Bug Is a Privacy Disaster (CVE-2014-6041)

#51
post #37

I am a big Linux fan and appreciate the openness and control that I can get with Android as opposed to Apple and Microsoft products, but... My Android experience has been shit, and I'm really getting sick of it. Admittedly, much or even most of the problem for me is the OEMs screwing things up and not sending out updates.

You're not the only one. I'm sorry, but the Android issue has devolved into a holy war but...

.. support is terrible on the Android side. Really terrible.

Re: Major Android Bug Is a Privacy Disaster (CVE-2014-6041)

#52
post #11

So the bug is only for a browser that isn't supported by Google? No surprise that it hasn't been patched. If security is such a big deal to a user they should use a browser that is supported by a strong development team. Firefox and Opera Mobile work fine on low end phones.

Pretty much the tone-deaf reaction I was expecting. Thanks! (Of course, these devices will still be counted by those touting Android's market share. Surprise surprise)

And this is where platform evangelism/favortism morphs from the merely annoying to the (potentially) dangerous.

Re: Major Android Bug Is a Privacy Disaster (CVE-2014-6041)

#53
post #29
post #26

Earlier quoted context omitted.

https://code.google.com/p/chromium/wiki/AndroidBuildInstruct...

That's not chrome.

It is very very close: https://code.google.com/p/chromium/wiki/ChromiumBrowserVsGoo...

tl;dr: Chromium is Chrome minus:

1. Crash/usage reporting to Google.

2. Proprietary video format support

3. Embedded Flash implementation (which doesn't exist on mobile anyway).

4. Google API keys.

If what you care about is security auditability, that's pretty good. If you care about running only open source software, that's going to be very hard to do in the Android/Google-Play ecosystem.

Re: Major Android Bug Is a Privacy Disaster (CVE-2014-6041)

#54
post #48

It's this sort of thing that puts me off Android as a platform. Even my mother got sold a 2.2 handset recently (Samsung Galaxy Ace) that hasn't been patched for the best part of 3 years. You never know when you're going to end up with a lemon on your hands. Big jump to this conclusion but I'm more inclined to trust Microsoft at the moment as they have a better reputation for lifetime (unlike Android), have a very pub…

I don't understand why people are surprised they might be sold an inferior product if they don't do a minimum of research.

That's not how salespeople work...

Re: Major Android Bug Is a Privacy Disaster (CVE-2014-6041)

#55
post #26
post #19

Earlier quoted context omitted.

Use Firefox. Why? Chrome isn't open source, if you care about that kind of thing. And personal preference also.

https://code.google.com/p/chromium/wiki/AndroidBuildInstruct...

Is the Android chrome (in the UI sense) now open source as well? If that is the case, we could finally get the option to disable third-party-cookies...

Re: Major Android Bug Is a Privacy Disaster (CVE-2014-6041)

#56
Replaced by Chrome ("that giant hog").

I'm on a slightly older phone, but I actually removed Chrome from it not long ago. I started having problems with updating apps due to insufficient space, and while I have a fair amount of crap installed, I also have ~2.5GB of "Phone" storage for apps so I started investigating (this is separate from "sdcard" data storage which is ~8GB). Turns out Chrome, at least on the HTC Amaze 4G with 4.0.3, takes up about 250MB - my largest installed app by about a factor of 4 (next largest was ~80MB). This was not cache or data, this was the app itself.

I don't know what all they've moved into there as part of their push to cripple Android except as a host for the "Google Play Ecosystem," but crap like this is not endearing.

Re: Major Android Bug Is a Privacy Disaster (CVE-2014-6041)

#57

It's this sort of thing that puts me off Android as a platform. Even my mother got sold a 2.2 handset recently (Samsung Galaxy Ace) that hasn't been patched for the best part of 3 years. You never know when you're going to end up with a lemon on your hands. Big jump to this conclusion but I'm more inclined to trust Microsoft at the moment as they have a better reputation for lifetime (unlike Android), have a very pub…

[deleted]

Re: Major Android Bug Is a Privacy Disaster (CVE-2014-6041)

#58

Replaced by Chrome ("that giant hog"). I'm on a slightly older phone, but I actually removed Chrome from it not long ago. I started having problems with updating apps due to insufficient space, and while I have a fair amount of crap installed, I also have ~2.5GB of "Phone" storage for apps so I started investigating (this is separate from "sdcard" data storage which is ~8GB). Turns out Chrome, at least on the HTC Ama…

google is learning how to be evil with offline tech.

online they just shutdown the old system. offline now they leave holes and announce them when they want you to upgrade. "for security"

Re: Major Android Bug Is a Privacy Disaster (CVE-2014-6041)

#59
post #17

Earlier quoted context omitted.

Android One is meant to make it simple for lo-end OEMs to ship high quality implementations of up-to-date Android and keep up with new releases. It's hard to migrate a huge OEM ecosystem to that kind of program quickly.

I doubt that will happen. At $100 a handset where is the return and motivation for an OEM to bother pushing updates out for firmware/integration testing etc (that the telcos require)? Look at the aforementioned Galaxy Ace in my last comment which is exactly where this will end up, yet again. Also, they say 2 years' support. If you look at the phone recycling business, there is 4-5 years life in a franken-handset ship…

Google's providing the OS support -- they make money on you using their services. Even if the revenue per user is only ¢10/year, when you get 100's of millions to billions of users that adds up.

Re: Major Android Bug Is a Privacy Disaster (CVE-2014-6041)

#60

If you aren't familiar with SOP, this is about the worst "stupid web vuln" that can happen. SOP is the glue that kind of almost makes the web secure. The attack DOES work if X-Frame-Options is enabled (thanks joev. The msfmodule says so clearly). ALL sites with or without XFrameOptions can be loaded in an iframe, and sent to a bad guy. If you would like to test on your device/browser, you can on ejj.io/SOP.php . If y…

good old blacklist instead of whitelist.

why forbid javascript: and some other thing that you know know, if you know for sure you only want http or https?

always allow what you know for sure how to handle instead of denying what you think you know that you don't want.

Post reply on HN