News for hackers. Stuff that matters.
Re:Google discloses three severe vulnerabilities in Apple OS X by giovannibajo1 on Friday January 23, 2015 @09:44PM (#8938637)
They would fix any doubt if they began releasing bugs and exploits for Android as well.
Re:Google discloses three severe vulnerabilities in Apple OS X by notatoad on Friday January 23, 2015 @09:59PM (#8938665)
Better that they fix their own vulnerabilities than release them.

They do offer a bug bounty for their own products, to encourage third parties to do to them exactly what they're doing to Apple and Microsoft.

Re:Google discloses three severe vulnerabilities in Apple OS X by timonovici on Saturday January 24, 2015 @07:05AM (#8939399)
It's not like they sit around and say: "Oh, f*ck Android, let's find vulnerabilities in other operating systems." I suppose it's long since they have a team working on Android vulnerabilities, but it's not trivial fixing, deploying - not to mention finding the flaws.
Re:Google discloses three severe vulnerabilities in Apple OS X by fidotron on Saturday January 24, 2015 @12:04PM (#8940139)
When it comes to others they have total disregard as to how difficult to deploy any fix is. The same standard should apply to themselves, but clearly doesn't.
Re:Google discloses three severe vulnerabilities in Apple OS X by danieldk on Saturday January 24, 2015 @05:10AM (#8939281)
For a start, they could try to fix vulnerabilities in Jelly Bean's webview[1] and urge manufacturers and carriers to push updates to their phones, since 46% of the market is apparently still Jelly Bean[2]

Of course, it's an uphill battle with the manufacturers/carriers. But as long as Google is not applying fixes to Jelly Bean, the manufacturers can always blame Google.

[1] http://www.androidpolice.com/2015/01/23/google-issues-offici...

[2] https://developer.android.com/about/dashboards/index.html

Re:Google discloses three severe vulnerabilities in Apple OS X by divegeek on Saturday January 24, 2015 @10:44AM (#8939861)
The Android security lead has posted a statement on this issue, explaining what is and is not being done, and why: https://plus.google.com/u/0/+AdrianLudwig/posts/1md7ruEwBLF