Tag Archives: html5

New Chromium now supports Netflix natively without Wine plugins


The latest update to my Chromium package is an interesting one. It took me many nights, all of last week, to find a solution for a crash that is mentioned in various bug reports and for which I could not find a working fix anywhere. In the end, I just removed the few lines of code which trigger the crash.

Dear Google: I think it is stupid to force a crash in my package just because my build is not an “official build”. If your developers want bug reports, fine, arrange something in your development or beta source code, but do not annoy users of your your stable releases by making your product unfit for Google searches.

Anyway, Chromium 37.0.2062.94 comes with a couple of critical bug fixes:

  • [$30000][386988] Critical CVE-2014-3176, CVE-2014-3177: A special reward to lokihardt@asrt for a combination of bugs in V8, IPC, sync, and extensions that can lead to remote code execution outside of the sandbox.
  • [$2000][369860] High CVE-2014-3168: Use-after-free in SVG. Credit to cloudfuzzer.
  • [$2000][387389] High CVE-2014-3169: Use-after-free in DOM. Credit to Andrzej Dyjak.
  • [$1000][390624] High CVE-2014-3170: Extension permission dialog spoofing. Credit to Rob Wu.
  • [$4000][390928] High CVE-2014-3171: Use-after-free in bindings. Credit to cloudfuzzer.
  • [$1500][367567] Medium CVE-2014-3172: Issue related to extension debugging. Credit to Eli Grey.
  • [$2000][376951] Medium CVE-2014-3173: Uninitialized memory read in WebGL. Credit to jmuizelaar.
  • [$500][389219] Medium CVE-2014-3174: Uninitialized memory read in Web Audio. Credit to Atte Kettunen from OUSPG.

New in Chromium 37:

Two nice things happened in Chromium 37 that I want to write about.

  • A separate PDF plugin is no longer needed. This release of Chromium finally has the PDF library included which in the past would only be released with the binary Chrome builds. PDF’s are now nicely rendered in the browser window without having to install the chromium-pdf-plugin package. In fact, I removed that plugin package from my repository. If anyone still wants or needs the SlackBuild for that, let me know and I will post it somewhere.
  • I have not tried it myself (no Netflix here) but reportedly Chrome 37.0.2062.94 can play Netflix natively in Linux, without the need for Wine plugins that add support for MS SilverLight. The new HTML5 player with DRM which Netflix optionally uses now, is supported thanks to co-operation between Chrome developers and Netflix. I assume that the Chromium package would provide the same support. In any case, newer (developer) versions of Chromium reportedly do support Netflix natively, just not sure of the exact version where this started working. Try it, and tell me what you found! I will release a “chromium-dev” package later this week to allow testing in Slackware of new functionality, that may help too.

How to make Netflix work with Chrome/Chromium?

These are instructions I took from a LinuxQuestions.org thread, again I am unable to verify their value.

  • Install Chromium (Chrome would work too of course)
  • Install a User Agent switcher (apparently Netflix keeps blocking Linux browsers even though they now support them…)
  • Add new User-Agent in User-Agent-plugin with following settings:
    • New User-Agent Name = Netflix
      New User-Agent String = Mozilla/5.0 (Windows NT 6.3; Win 64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.24 Safari/537.36 (looks like 37.x.x.x version numberss do not work; use the latest Chrome (beta) version here).
      Group = Chrome
      Append = Replace
      Indicator Flag = NX (or whatever you want)
  • Add a new Permanent Spoof List
    • Domain = netflix.com
      User-Agent String = Netflix
  • Make sure your mozilla-nss package has at least version 3.16.4 (Pat Volkerding upgraded all mozilla-nss packages in recent Slackware releases for this reason)
  • In Netflix Playback-settings chose HTML5

Have fun! Eric

Note (added Fri Jan  9 12:12:23 UTC 2015):
Please also read my follow-up article because I have made the Widevnie plugin actually work with Chromium and watching Netflix is now possible in Chromium without any UserAgent spoofing.

Google Open Sources VP8 Codec

The press has seen a lot of commotion lately about HTML5 and its out-of-the-box video support through the new < video > tag.

Ogg Video – being the open source and royalty-free container used for the HTML5 video tag – is not favoured by the big players with commercial interests in web standards and content. There is really only one alternative to Ogg’s Theora video codec which is widely accepted: and that is the H.264 codec used for instance in Apple’s MP4/Quicktime video container.

But H264 video (also well-known because Youtube streams its content in H.264) is not royalty- or patent-free. The MPEG-LA company has formed a patent pool for H.264 and administers license fees for its use in applications and appliances.

However it was decided that creating, distributing and viewing Internet H.264 video content is royalty-free until at least the year 2015, as long as that content is being made freely available. A lot of people interpret this ruling as “H.264 is a free and open standard“… but this is not true. The patent holders (Microsoft and Apple being part of that group) maintain that even after 2015, H.264 video will stay free from royalty fees. I don’t know about you, but those two companies are among the ones I do not trust at all when they make statements like that.

So, a lot of folk kept an eye on Google after that company acquired On2, the creator of the VP8 video codec (and several more). On2 had already opensourced one of their older video codecs. This was their VP3 codec which was given to the Xiph.Org foundation and became…. the Theora codec. It was rumoured that Google would let history repeat itself and opensource VP8. And today, that has indeed happened.

Google announced that they release the VP8 video codec under a royalty-free open-source license. They have defined a new video container, called WebM, which will use VP8 for video  and Ogg Vorbis for the audio stream. Basically, WebM is a Matroska container (MKV) with some restrictions. The image quality and compression rate of VP8 is comparable to that of H.264, something which can not be said about Theora. I believe that this new video format is destined to become the true rival to H.264 in HTML5.

Microsoft had recently announced that they would only support H.264 video in their implementation of HTML5, but the company stated today that it prepares to add support for the VP8 video codec in Internet Explorer 9. IE9 will use the VP8 codec… if the user has installed it on Windows. Well, it’s a start. And Adobe plans to include VP8 in the Flash 10.1 player. They have to, after the crusade started by Microsoft and Apple to replace Flash Video on the web with H.264.

Interesting times ahead! Now, what would happen if Google decided to switch Youtube’s videos from H.264 to VP8? That would be a big statement. If they plan this, it will be like droppping a bomb in the cradle of Internet content providers.

VideoLAN’s VLC media player (one of my favourite open source projects) already has the code to support VP8 once that codec gets added to ffmpeg, the engine of so many media players. The VideoLAN foundation also hosts the open source x264 encoder which is arguably the best free H.264 encoder available. There will be freedom of choice, people! That is always commendable.

Speaking about freedom – I am praising this Google initiative of course, but I do not want to be negative about Ogg. A lot of people seem to complain about it’s shortcomings but it was – and is – a truely free video container format. If not for Google and their VP8, the Ogg format would still be the only choice for truely free content creation. I totally love Xiph.Org. Read this excellent article by the hand of its chief engineer Monty (Christopher Montgomery) in which he defends what is dear to him: http://people.xiph.org/~xiphmont/lj-pseudocut/o-response-1.html

And now, time for a beer.