Package Details: chromium-widevine 1:4.10.1610.0-1

Git Clone URL: https://aur.archlinux.org/chromium-widevine.git (read-only, click to copy)
Package Base: chromium-widevine
Description: A browser plugin designed for the viewing of premium video content
Upstream URL: https://www.widevine.com/
Keywords: amazon chrome netflix prime webengine
Licenses: custom
Conflicts: chromium-widevine-dev
Provides: chromium-widevine-dev=4.10.1610.0
Submitter: Scimmia
Maintainer: Scimmia
Last Packager: Scimmia
Votes: 389
Popularity: 4.34
First Submitted: 2015-04-17 05:05
Last Updated: 2020-01-16 21:47

Latest Comments

1 2 3 4 5 6 ... Next › Last »

chrisco23 commented on 2020-01-17 12:20

At some point Netflix stopped working in my Chromium even with this AUR package. Everything I google just points me back to this package (installed and has been for a long time). Tired of running Firefox (or Chrome) for this sole purpose. Anybody have any ideas? Thanks.

Vrakfall commented on 2019-10-29 16:15

Ah you're right, thanks.

(Tho, said AUR helper is made by a TU :x )

Scimmia commented on 2019-10-29 14:56

Sounds like a crappy AUR helper. Works fine with makepkg.

Vrakfall commented on 2019-10-29 14:26

I've got these errors now if I try to build:

==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace.
==> ERROR: pkgver() generated an invalid version: ==> Starting pkgver()...
4.10.1582.1

Scimmia commented on 2019-10-20 18:00

Looks like that change was made in chrome 78, which should be released in a matter of days. I think we'll wait for that and switch it all at once.

sl1pkn07 commented on 2019-10-20 13:23

Hi

please add also the new widevine structure comes with the chrome unstable (+79) until the stable merge it

https://chromium-review.googlesource.com/c/chromium/src/+/1808309

diff --git a/PKGBUILD b/PKGBUILD
index 3a6b542..2564ea2 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -17,13 +17,21 @@ conflicts=('chromium-widevine-dev')
 options=('!strip')
 source=("chrome-eula_text-$_license_date.html::https://www.google.com/intl/en/chrome/privacy/eula_text.html"
         "https://dl.google.com/linux/deb/pool/main/g/google-chrome-stable/google-chrome-stable_${_chrome_ver}-1_amd64.deb"
+        "https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-unstable/google-chrome-unstable_79.0.3938.0-1_amd64.deb"
         get_cdm_version.c)
 sha256sums=('SKIP'
             '07abdccd7c15f5abe68765c1162f2ab666b6478a4d578aa6351d5667cd983a48'
+            '9582f71c706d2de597fd9ca3e689e904cf43163911a8b3d81eb071eb27b1dff4'
             '3fda44a5b8b222434530f27923568de1fda1eb0caa8621b56a8b2a6a2a2e3d5d')
+noextract=("google-chrome-stable_${_chrome_ver}-1_amd64.deb"
+           'google-chrome-unstable_79.0.3938.0-1_amd64.deb')

 prepare() {
+  bsdtar -x -f google-chrome-unstable_79.0.3938.0-1_amd64.deb data.tar.xz
+  bsdtar -x --strip-components 4 -f data.tar.xz opt/google/chrome-unstable/WidevineCdm
+  bsdtar -x -f "google-chrome-stable_${_chrome_ver}-1_amd64.deb" data.tar.xz
   bsdtar -x --strip-components 4 -f data.tar.xz opt/google/chrome/libwidevinecdm.so
+
   gcc get_cdm_version.c -o get_cdm_version -ldl
 }

@@ -33,7 +41,6 @@ pkgver() {

 package() {
   install -Dm644 libwidevinecdm.so -t "$pkgdir/usr/lib/chromium/"
-  install -d "$pkgdir/usr/lib/chromium-dev/"
-  ln -s ../chromium/libwidevinecdm.so "$pkgdir/usr/lib/chromium-dev/libwidevinecdm.so"
+  for i in $(find WidevineCdm -type f); do install -Dm644 "${i}" "$pkgdir/usr/lib/chromium-dev/${i}"; done
   install -Dm644 chrome-eula_text-$_license_date.html "$pkgdir/usr/share/licenses/$pkgname/eula_text.html"
 }

https://i.ibb.co/vHQdQdN/Screenshot-20191020-152201.png

dqnh commented on 2019-10-18 18:59

If you really want to verify the contents of chrome-eula_text you could use something like sed 's/nonce=\".*\"//' but I don't think there is any point doing that since this is just a harmless EULA. Besides, you still would have to SKIP it and put the check elsewhere.

Vrakfall commented on 2019-10-18 14:37

Which seems to have been changed again? Or am I hallucinating?

Scimmia commented on 2019-10-18 14:00

Yes, nonce is going to be a real problem. I really don't like using SKIP for files, but I'm not seeing a good alternative in this case.

Segaja commented on 2019-10-18 13:41

From a security standpoint it makes no sense to calculate the checksum of a file that was just downloaded. IF the upstream server was compromised you would never know because you use the hash you just calculated from a corrupt file.

If you don't care about the hash (because it is an EULA file which is only in the package for legal reasons) you would be better of using just "SKIP" in the place of the checksum in the sha256sums array.