unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@n0.is>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 34565@debbugs.gnu.org
Subject: bug#34565: ungoogled-chromium contains Widevine DRM
Date: Sat, 12 Oct 2019 11:14:17 +0000	[thread overview]
Message-ID: <20191012111417.bqw7xynqpcqtawgx@uptimegirl> (raw)
In-Reply-To: <87sgwims6k.fsf@fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]

Marius Bakke transcribed 1.2K bytes:
> Giovanni Biscuolo <g@xelera.eu> writes:
> 
> > Hello,
> >
> > maybe Marius Bakke have something interesting to say about his
> > judgements on this "DRM matter"
> 
> [...]
> 
> > to sum it up: AFAIU for users to be able to use Widevine they must
> > create a custom package definition _outside_ official Guix channels
> > *and* download the shared object "libwidevinecdm.so" from Chromium,
> > installing it "manually" system wide or locally
> 
> This analysis is correct.  For DRM to work, the user has to build with
> "enable_widevine=true", and then somehow obtain 'libwidevinecdm.so' and
> make the browser use it.

Can this bug be closed?
The wording is very vague ("may") and for Guix to distribute widevine.so
legally, you have to get permission and sign an NDA with Google, both of
which are reportedly hard for 3rd party devs even, not sure how hard it is
for new operating systems. Your stand on software with NDAs should be clear
(as per policy not applicable, no NDAs).
So even if traces of the code to build this might still be left, you have
to master additional steps to make it work, and after having read some
of widevine.so I doubt it would work out of the box with Guix System
(elfpatching could get it to work with Guix, but you are still entering
the field where official distribution requires legal paperwork).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-10-12 11:15 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
2019-02-20  9:22           ` Giovanni Biscuolo
2019-02-20 14:48             ` Marius Bakke
2019-10-12 11:14               ` ng0 [this message]
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191012111417.bqw7xynqpcqtawgx@uptimegirl \
    --to=ng0@n0.is \
    --cc=34565@debbugs.gnu.org \
    --cc=mbakke@fastmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).