From: Leo Famulari <leo@famulari.name>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 34565@debbugs.gnu.org
Subject: bug#34565: ungoogled-chromium contains Widevine DRM
Date: Wed, 20 Feb 2019 00:42:19 -0500 [thread overview]
Message-ID: <20190220054219.GA9386@jasmine.lan> (raw)
In-Reply-To: <aba259a44a52136939babd3f3cfee6be@lepiller.eu>
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
On Tue, Feb 19, 2019 at 03:44:17PM +0100, Julien Lepiller wrote:
> So I've downloaded the source tarball with `guix build -S chromium`
> and here's what I found in it:
[...]
Thanks for taking a look, Julien!
We need to find out if Widevine DRM is actually included in the Guix
ungoogled-chromium package or not.
Obviously the intent was to not include it, and it does not work in
practice. Widevine videos do not play and there is no prompt to install
or enable DRM, unlike in some other browsers that use DRM.
I think the next steps for this subject are to first, in general, figure
out where Widevine comes from, and then, more specifically, decide what
to do about the files you mentioned.
As I mentioned already, other distros seem to get Widevine by extracting
its binary from Chrome, even when using it for Chromium. It seems
reasonable to assume that if Widevine were included in Chromium they
would not be downloading a whole 'nother browser for that one component.
As for the specific files listed by Julien, they may be harmless, or
not, we should figure out what they do and if they need to be removed.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-20 5:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 3:44 bug#34565: ungoogled-chromium contains Widevine DRM Jason Self
2019-02-19 7:06 ` Leo Famulari
2019-02-19 13:28 ` Jason Self
2019-02-19 13:42 ` Julien Lepiller
2019-02-19 14:44 ` Julien Lepiller
2019-02-20 5:42 ` Leo Famulari [this message]
2019-02-20 9:22 ` Giovanni Biscuolo
2019-02-20 14:48 ` Marius Bakke
2019-10-12 11:14 ` ng0
2019-10-12 11:32 ` bug#34565: ungoogled-chromium may contain " Marius Bakke
2019-02-19 14:43 ` bug#34565: ungoogled-chromium contains " Leo Famulari
2019-02-20 0:39 ` Jason Self
2019-02-20 1:12 ` Jason Self
2019-02-20 1:19 ` Jason Self
2019-02-20 13:03 ` Jason Self
2019-02-20 16:18 ` Julien Lepiller
2019-02-20 20:15 ` Adonay Felipe Nogueira
2019-02-20 21:49 ` Ricardo Wurmus
2019-02-21 2:19 ` Jason Self
2019-02-20 5:15 ` Leo Famulari
2019-02-20 5:35 ` Jason Self
2019-02-20 7:59 ` bug#34565: ungoogled-chromium might contain remnants of " Ricardo Wurmus
2019-02-20 10:09 ` bug#34565: ungoogled-chromium contains " Jelle Licht
2019-02-20 14:37 ` Marius Bakke
2019-02-21 2:43 ` Jason Self
2019-02-21 7:51 ` Marius Bakke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190220054219.GA9386@jasmine.lan \
--to=leo@famulari.name \
--cc=34565@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.