Google Pushes New Chrome Release, Pays $14k Bounty
Trailrunner7 writes "Google has released version 8.0.552.237 of its Chrome browser, which includes fixes for 16 security vulnerabilities. The company also paid out more than $14,000 in bug bounties for the flaws fixed in this release, including the first maximum reward of $3133.7. The new version of Google Chrome has fixes for 13 high-priority bugs, but the most serious vulnerability the company repaired in the browser is a critical flaw resulting from a stale pointer in the speech handling component of Chrome. That flaw, along with four others, was discovered by researcher Sergey Glazunov, who earned a total of more than $7,000 in rewards for the bugs he reported to Google."
1) Convince Microsoft to adopt similar bug strategy.
2) Start using software as it was designed to be used...
3) PROFIT!!
Yes, that's right. No step 4.
*sips coffee*
Moved to http://soylentnews.org/. You are invited to join us too!
It's just too sexy
I don't care how much it's for, because if I ever get a check from Google, it's getting framed. Just sayin.
being that I am running 9.0.597.19 I think you got your number wrong.
for identifying a series of bugs missed by Google's fabled (and pampered) FT engineering staff, that might otherwise come to the world's attention by customers being exploited for $$ by overseas hackers.
Someone in the trade press should work on an article about the "prize-sploitation" of top software engineers....
14K sounds like a pretty good deal for Google. That's less than 2 months of salary for even an intermediate tester.
"Hello google, i found a bug." "Did you fix it?" "Yeah here is 100 man hours of work and 1,000 lines of code" "k, cool, heres $10"
I've heard that h.264 support is broken in an upcoming release.
#DeleteChrome
To find out who is capable of finding the obvious ploys...
This issue is a bit more complicated than you think.
Perhaps I have been subjected to one too many script kiddies, but the total paid out looks suspicious...
3,133.7?
Looks suspiciously like 'leet to me. Now I'm surprised they didnt pay "Over 9,000" instead.
Is that updates take place silently and promptly without any user intervention even on systems with UAC activated (a copy is installed to %appdata%). Why can't other applications just keep themselves up to date automatically in that way? It's obviously not technologically impossible, we've seen it happen. Even Windows Update is vaguely alright in this respect once you disable the restart-nagging. Debian systems do fine after a simple 'apt-get update && apt-get upgrade -y' in the root crontab although the GUI will occasionally pester you.
Firefox has to be the worst offender in this respect, both in terms of actual software upgrades that block the UI and then add-ons that also block the main UI and then spawn a silly splash to inform you of the amazing upgrade rfom 2.1.6 to 2.1.6(b). Unless it requires a change in the terms of the license or more permissions (Android does this nicely), I don't care and I definitely don't need to be interrupted to see it.
Another free tip for the Mozilla team -- when I open an application is not the time to install any updates. In fact, that is the only time you can be nearly guaranteed that I want to use the application right this second. Schedule updates for when I close the app because it's pretty damn likely I don't need to use it for a few minutes.
Apple could learn the same thing about their infernal updates too, plus an extra special place in hell for pimping their other software at the same time. I still get calls from my parents "Do I need Safari?", hmm, no just upgrade iTunes when it asks you to. "What about quicktime?". Gah.
I prefer that as my video playback of choice. I don't want want the sub par solution.
I like big butts and I cannot lie.
And what makes this bug security related? :)
Because the reality is that with h.264 support out, rather than double up all encoding efforts for WebM sites will simply make Chrome use Flash players with h.264 videos.
Have you SEEN the security advisories around Flash?
"There is more worth loving than we have strength to love." - Brian Jay Stanley
It's just a company, dude.
I hate Flash video. In any browser I use, I deploy Flash Block or something like it to save resources.
The effect of Chrome removing h.264 video support has one direct effect - balkanization of the HTML5 <video> tag to where no-one is going to use it, thus forcing the re-appearance of Flash video in a lot of places it was starting to recede from.
I refuse to support backwards movement in standards. Yes WebM is an open standard - but one controlled by Google. At least h.264 has a much wider range of companies backing and directing it. The bigger open standard to worry about to my mind is support of the <video> tag so we can let browsers innovate around support for video playback rather than be forced to use whatever horror a partiular website has chosen to craft in Flash to view videos with. After is in comfortable use, then let's get widespread WebM support and try to move the industry there - Google is killing two birds (WebM by too early adoption and <video> by afore-mentioned market splintering) with one stone, and I'll not give them money to buy another sling.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Certainly having a trouble free product is worth more than 10% of developer salary to google?
Why not just scan it? Then you can frame the print out (hell, you can even print 10x larger), and mail the check to me. That way we both win. Google on your wall. Money in my pocket.
Will they never learn?
-- Braden's law of data: All data spends some of its lifetime in an excel spreadsheet.
If I'm closing the browser, that probably means my battery is dying. My UPS is doing the extra-fast beeping that happens right before it cuts out.
That would be the absolute worst time to update. The power will cut out right in the middle of the update. Few software projects can reliably avoid self-corruption when that happens.
Firefox has very nice bookmark separators which can keep groups of bookmarks nicely together.
However, Google has been stubborn as hell over this. They will not create bookmark separators.
I bet all techies and hardcore web users will not switch to Chrome over this. People on the web are
saying as much.
It is amazing that they are so adamant over this one feature. You know, I don't like that attitude.
Later Chrome...
You know, for a company with a total equity of US $36.004 billion (2009) the sum of $14,000 being spent to improve their product doesn't seem that good of a deal for the people doing the work...
Depends, Canine Age 3 = Human Age 28 Years. You didn't state species :)
I personally can't stand the way windows insists on installing its updtes on shutdown. When I say shutdown, I mean shutdown -- not "dick around for 20 minutes and THEN shutdown". I consider this a bug, and a very annoying one at that.
So...how many of these apply to the mobile browser in Android? ...and how many people are never going to get a fixed version of their phone's browser, because the phones have been abandoned by the manufacturer less than 12 months after purchase? (or even before, like the phones still shipping with Android 1.5 or 1.6)
For a product claiming to be "8.x", it sure could use a lot of refinement. They haven't accomplished anything special with the tab interface (the biggest reason I can't adopt it for primary use -- I need Panorama and if not that, at least vertical nested tree tabs).
..ouch, my mind hurts!
Where, when you print a page, you have no control over the page layout. You're stuck with cut-off URLs in the corner, etc.
The most simple thing, and Google has overlooked it for years. Morons.
They should have made the maximum reward $1337.
eleet actually...
For maximum compatibility, here’s what your video workflow will look like:
Companies are not going to go for maximum compatibility that costs too much. They are going to go for the maximum compatibility at minimum cost. So let's revise your workflow to predict what will really happen:
1. Make a version that uses H.264 baseline video and AAC “low complexity” audio in an MP4 container.
2. Link to all three video files from a single element, and fall back to a Flash-based video player.
This workflow supports as many systems and browsers as yours does, at half the storage space and half the encoding time.
Convince me. Why would anyone convert to WebM when they can just play h.264 in a flash player on Chrome or any other browser that doesn't support h.264 directly?
Remember that Google controls Flash, because the whole chain of events pushes more use of flash players they have zero incentive to remove h.264 support from Flash.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
H264 may have much wider backing in some fields but that's just not visible in the browser usage share: After Googles decision I guess around 1% of the browsing happens on a browser capable of HTML5 + H.264.
The direct result of that is zero adoption of the HTML5 video tag. There is no game afoot; the game is over, Google took the ball home.
When you can just wrap h.264 video in a Flash player for computers and thus support iOS devices and all browsers with one file, why would you do ANYTHING else?
"There is more worth loving than we have strength to love." - Brian Jay Stanley
They're doing two releases a quarter
I'm pretty sure the announced release schedule is one release every six weeks (which is 2 in 12 weeks), which is a little faster than 2/quarter (which is 2 in 13 weeks.)
to be honest it can wait till i feel like my computer can be on while the bowser is closed; as rare as that be
i dont see a problem as long as its not months behind
Bowser? Then maybe Chrome can update itself while you play Wii.
Pasting into a textarea on a "/comments.pl" page works more often than pasting into a textarea on a "/story/" page. Try opening the comment to which you want to reply (e.g. #34876160) in a new tab and clicking "Reply to This" there.
Pasting into an empty textarea is also more reliable. If you can't use the first workaround because you're trying to add a top-level comment, it might even work to paste from gvim, gedit, etc. if the textarea is empty.