Oh dear. We ignored yesterday’s CRAZED REPORTS of possible breaches of Android password security over open wi-fi connections, as it appeared the vulnerability was purely theoretical – and no one had actually confirmed any possible password breaches out in the real world.
But that fact hasn’t stopped UK free paper Metro from going big with the news, spreading it across its front page today:
The original report which sparked all this fuss can be found here. The Android ClientLogin flaw is apparently fixed in Android 2.3.4 which pretty much nobody has yet.



Jorge
/ May 18, 2011I’ve got 2.3.4! The phone to have of January 2011 (ages ago!) has one small plus point over the current crop of super phones. There, I’m not sulking too much being stuck with a Nexus S for the next 18 months….
Great Uncle Mentuss
/ May 18, 2011I’ve still got my Nexus One, and I’m not getting rid until there’s a more powerful Google devphone of similar excellence. I didn’t dig the S.
But still, gotta love the fact we get firmwares months before everyone else, eh?
mintvilla
/ May 18, 2011i only upgrade to phones that are supported by the cyanogen team. So i have 2.3.4 on my LG o2x
Great Uncle Mentuss
/ May 18, 2011Actually, I got on the cyanogen train as soon as they moved to Gingerbread, I’d been using a stock AOSP gingerbread ROM before that.
As far as I’m aware the N1 is still the “lead” platform for CM (with Cyanogen maintaining it himself)
The only problem with updating to the latest and greatest if there isn’t an stock version of the same build of Android for your device, is modders have to work around the fact there are no new propriety drivers for the hardware, using drivers from the most recent official ROM for your device as a workaround.
There was a significant difference in CyanogenMod 7′s performance after the N1 finally got an official OTA Gingerbread update (2.3.2), and they could roll the new drivers into their build.
mintvilla
/ May 19, 2011yh i know, i had the desire, which required the nexus 1′s drivers to be perfect as it had the exact same internals as the nexus. So it was always the same, google release a new version of android, the cm team get out a nightly with some bugs, then wait for the ota nexus1 release, then cm would become perfect.
the reason i plumped for the LG02x was mainly as in america its branded as the G2x, and doesnt run LG’s rubbish software, but infact runs stock android. And for that theres a leaked build of gingerbread for that so its going quite well, still at nightly stage but i dont really have any bugs to be honest so am made up with the Lgo2x
Mark
/ May 18, 2011The scourge of irresponsible reporting continues.
Can’t these sites/newspapers be done for libel? Don’t they have a responsibility to check for factual accuracy before reporting.
I suggest Google sue their asses…
Simon
/ May 18, 2011It’s the Metro, which is owned by the Daily Mail (well, Associated Newspapers Ltd actually). You should never expect ‘accurate’ or ‘balanced’ reporting from them.
Also the PCC states the headline isn’t part of the article and therefore doesn’t need to actually be accurate. Massive loophole :(
Simon
/ May 18, 2011I haven’t read the entire report (although I will, I’m into thinks like this) but I believe the problem occurs when connected to an unsecured WiFi network. Yes Google needs to fix the issue, but nothing is secure over an unsecured WiFi network.
UKAndroid
/ May 18, 2011Hardly a serious mainstream paper – it’s a throwaway free sheet mainly for Londoners.
Gary C
/ May 18, 2011“…making it the UK’s fourth largest daily newspaper, after The Sun, the Daily Mail and the Daily Mirror, although it is closing in on the Daily Mirror in terms of distribution”
http://en.wikipedia.org/wiki/Metro_(British_newspaper)
Rik Hemsley
/ May 18, 20112.3.4 here on N1 too. Didn’t notice until this article prompted me to check.