Comment
The change is a straightforward version bump in .SRCINFO for the Widevine CRX3 source, with the source still using HTTPS on Google's official chrome_component release path and no new build-time logic, scripts, or packaging metadata changes. I don't see any added persistence, privilege escalation, or integrity red flags in this diff alone. The only notable risk is the usual trust in a prebuilt proprietary binary blob from upstream, but that was already present before and is not introduced by this change.
@@ -1,14 +1,14 @@
pkgbase = chromium-widevine
pkgdesc = A browser plugin designed for the viewing of premium video content
- pkgver = 4.10.2934.0
+ pkgver = 4.10.3050.0
pkgrel = 1
epoch = 1
url = https://www.widevine.com/
arch = x86_64
license = custom
options = !strip
- source = https://www.google.com/dl/release2/chrome_component/accssjtqfpf5qicscrptql4jyyxa_4.10.2934.0/oimompecagnajdejgnnjijobebaeigek_4.10.2934.0_linux_ph722a3wl2goebkpserszm6bde.crx3
- sha256sums = d36111684f13d2f76f181eb0117a873e12e4ee6f0f9a3027a9d022b787d74eb2
+ source = https://www.google.com/dl/release2/chrome_component/bywu6vkyg6gmcthxdaetzfkptm_4.10.3050.0/oimompecagnajdejgnnjijobebaeigek_4.10.3050.0_linux_aduyhcxcs7a2znuo6ss5tffn5jpa.crx3
+ sha256sums = b70d887771d663018f46b1072b14320bd8b9a763641ef0317bd979cbad443e88
pkgname = chromium-widevine
depends = gcc-libs