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!
I don't care how much it's for, because if I ever get a check from Google, it's getting framed. Just sayin.
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
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.
My Chrome goes to 11.
When you're afraid to download music illegally in your own home, then the terrorists have won!
Way to spot 'em, Captain Obvious.
Yea, they fixed it alright. They got rid of it.
http://www.pcmag.com/article2/0,2817,2375719,00.asp
Sometimes the light at the end of the tunnel is the headlight of an oncoming train.
It's just a company, dude.
I posted this URL in another thread, but it is a great view of the whole video format "war" going on.
Even with chrome supporting h.264, in order to get maximum compatibility for video playback across all browsers(let's not leave out Android and Iphone), you still need to have the video in all 3 formats(below is copy/pasted from the site). Chrome isn't going "backwards" compared to where it stands now, unless you prefer having site visitors standardize on a set of browsers, in which case I can't argue with that:
For maximum compatibility, here’s what your video workflow will look like:
1. Make one version that uses WebM (VP8 + Vorbis).
2. Make another version that uses H.264 baseline video and AAC “low complexity” audio in an MP4 container.
3. Make another version that uses Theora video and Vorbis audio in an Ogg container.
4. Link to all three video files from a single element, and fall back to a Flash-based video player.
http://www.diveintohtml5.org/video.html