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.
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"
You're on a beta. Mine says 10.0.639.0.
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.
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!
Um, did you read the summary? They paid that Sergey guy OVER 9000!!1
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.
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.
Certainly having a trouble free product is worth more than 10% of developer salary to google?
Well, considering Chrome 1.0 was just released two years ago, we'll be on Chrome 12x by the end of the year.
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.
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...
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
It's even color-coded on the Chrome release blog.
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 :)
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!
Firefox and Opera don't support h264 either, why hate just on Google? and if you really cared about choice you'd be ranting on Microsoft for not supporting WebM in IE9. Yay more IE hacks! Guess you're not a web developer..
Like who? Apple and Microsoft?
What about Firefox and Opera. That's three against two right there that are backing it.
They should have made the maximum reward $1337.
You have locked your self into the Apple walled garden didn't you. Personally next month I will be watching WebM videos on youtube through firefox :).
For an extra $5,000 I'll give you one that goes to 12.
"This post contains words, known to the State of California to cause thought. Wash brain thoroughly after reading."
Your implying that Apple and Microsoft wouldn't simply support WebM. Where are the announcement "More the Merrier". Its not like there is not more than one language in the world ;). They don't and we both know why and the reasons stink!
I'll use flash for my HTML4 needs and look forward to WebM for my HTML5 and web developers who don't support this will not be getting my page views. I also look forward to better...and hopefully truly open video codecs in the future.
Firefox and Opera not only are supporting it. Opera is the one who originally suggested the tag, and simply cannot afford the implementation that Apple, Microsoft are forcing on the world. Thank goodness there is a real alternative.
Firefox and Opera are NOT supporting h264 in the video tag.
http://www.conceivablytech.com/5155/business/mozilla-celebrates-google-webm-delays-firefox-4-beta-9/
Also Opera's support for h264 has nothing to do with money.
http://www.muktware.com/n/12/2011/661
I prefer that as my video playback of choice. I don't want want the sub par solution.
And Google have chosen their video playback of choice, and said why. Personally I'm looking forward to all those small commercial Videos we can see on the net now they have a real choice. I'm looking forward to all the tools that are already appearing that are able to support WebM simply because the cost(nothing in every way) from Major browsers to small hardware & software companies. Thank goodness they are offered a real choice
I look forward to the improved WebM2.0 and WebM3.0 as work is undoubtedly containing in and outside goodle on this current gen codec we have already seen innovation in it being used for still images. I look forward to it being used in video chat/Game recording.
I look forward to new patent unencumbered Video and Audio Codecs appearing on the landscape and those being used as well.
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
Nope, you'll be using a Flash player just like everyone else.
There is no "walled garden" on the desktop, just a browser intelligent enough to support a full complement of standards (I can play WebM through Quicktime with a plugin).
"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.
Your implication of my "implying" is wrong :)
I am SAYING as it currently stands(not the direction it is going), there is a lot of diversity in what it supported. As it stands, Google is not changing the landscape just because they are a big name,Firefox and Opera currently do not and will not support it which a LOT of people use.
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.
Step 2 of your proposed workflow requires affording the H.264 encoder and streaming licenses.* How should a typical ad-supported web site afford these?
* Or mass emigration.
Wrong.
First, for streaming. It was extended to 2015 for free streaming if the site was offering free videos to the end user. That has even more recently been extended indefinitely: http://www.appleinsider.com/articles/10/08/26/apple_supported_h_264_standard_gains_free_license_for_internet_video_use.html
Second, sites doesn't pay for H.264 licenses to encode. They would have to pay IF they are building their own encoders. Sites would normally have to pay for the encoder themselves, like any other regular commercial software. The software encoders are the one who has to pay the fee. If you still want to go on about sites paying...you can probably find "free" software to get past paying and truely solve your price problem :)
It was extended to 2015 for free streaming if the site was offering free videos to the end user.
Is it still considered "free" if it's ad-supported? Or in the case of a low-volume local business selling local-interest videos to local customers, is there a prohibitive minimum annual royalty per firm?
Sites would normally have to pay for the encoder themselves, like any other regular commercial software.
And how much does a good one of these cost?
Is it still considered "free" if it's ad-supported?
Yes.
Or in the case of a low-volume local business selling local-interest videos to local customers, is there a prohibitive minimum annual royalty per firm?
And how much does a good one of these cost?
Dude, using questions to bring in doubt and uncertainty is no way to debate. Questions should only be used if your trying to gauge someone else's POV(or you are trying to win over an audience, in which case kudos).
Regardless, I will leave this questions up to you to discover.