Google has started revealing details about the security flaw they patched in recent updates for the T-Mobile G1. Rich Cannings of the Android security team has come fourth to reveal details about the RC29 and RC30 update that Google has not previously announced.
Google acknowledged the security flaw in the Browser which was fixed recently in the RC29 update, but Cannings stated there were two other issues addressed in the update. Google fixed a security flaw that allowed people to bypass Android’s locking mechanism by booting the G1 in safe mode. Google has decided to wait until patches have been given to all users before disclosing all the details about updates. They plan on publishing fuller details on their Android Security Announcements group soon.
RC30 which was delivered about a week after RC29, fixed a rare root-console problem in Android that automatically send all keystrokes to the root shell as a command. The issue was found when a user tried to type the word “reboot” in a text message only to find the device rebooting itself. Google left in a feature that let programmers execute commands with a remote device that was attached via serial port. When no device is attached the keyboard was used to input these commands.
“We tried really hard to secure Android. This is definitely a big bug,” he said. “The reason why we consider it a large security issue is because root access on the device breaks our application sandbox.”
Also fixed in the RC30 update were two Webkit problems reported to Apple by iPhone users. The first issue was a buffer overrun problem that allowed attackers to gain control over the browser by simply putting a malicious code on a Web site. The second problem allowed people to read what is stored in the phone’s memory to gain access to Web site cookies, potentially allowing them to gain online privileges. “If you’re logged into a bank at that time, (an attacker) could steal your banking cookies,” Cannings said. steal your banking cookies,” Cannings said.
[Via CNET]
Back to the thread... I'm glad they don't disclose the nature of the problem until it has been fixed... why? Recent events... for example...
Microsoft sent out an update that causes the wallpaper to change to an image saying "Please purchase a official version of XP..." (Says something to that effect in different languages) on pirated versions of their OS...
Then a couple weeks later... there was articles written about a recent disclosure of a security issue found in Microsoft OS software.... the articles explained in detail what happened and where to get the update... What do you think happened next?
Some of those people who use the pirated version happen to be hackers (anyone surprised there?) Well what they did in retirbution to the recent events is used the info in the articles and dissected the update to figure out what the flaw was... then created a virus that would take advantage of that security issue on computers that did not get the update...
Basically Microsoft pissed off a lot of people and then the people found a way to retaliate because of the disclosures...
This is actually really recent... within the last two months...
So with this is mind I can understand why Google chose to do things this way... I would prefer it actually... Those who do not learn from past mistakes are bound to repeat it...
Neither are the suggestions that the update is transmitted via a text message.
Most probably, the phone itself checks with a Google server once every XX hours to see if there are any updates or other "info".
I have an unlocked G1 on a Norwegian provider who has no clue whatsoever that I am using a G1 on their network.
I received the RC30 update this morning (Central European Time).
I don't know if there are any tricks you can do to try to "force" the update to arrive, but when I got to bed last night I rebooted the phone (turned it completely off and on) and left it on my desk, plugged into the power cord, and with wifi on. When I woke up, the message about "an update is ready" (or something like that) was on the display.
I have used the phone for 6 days, and was until today on RC19.
~Christopher
Neither are the suggestions that the update is transmitted via a text message.
Most probably, the phone itself checks with a Google server once every XX hours to see if there are any updates or other "info".
I have an unlocked G1 on a Norwegian provider who has no clue whatsoever that I am using a G1 on their network.
I received the RC30 update this morning (Central European Time).
I don't know if there are any tricks you can do to try to "force" the update to arrive, but when I got to bed last night I rebooted the phone (turned it completely off and on) and left it on my desk, plugged into the power cord, and with wifi on. When I woke up, the message about "an update is ready" (or something like that) was on the display.
I have used the phone for 6 days, and was until today on RC19.
~Christopher
This is the case here in USA... As for anyone using a "jailbroken" phone I've read you must do the "modified" manual updates... It is entirely possible that it is different for UK... you may have recieved the update because it is linked to your gmail accout so it is entirely possible that Googles servers stepped in...
If google is smart they would offer the update in multiple ways... especially if some Andoird phones may come to the household market without a service provider but a required WIFI or Lan line... So good observation.