all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jason Self <j@jxself.org>
To: 34565@debbugs.gnu.org
Subject: bug#34565: ungoogled-chromium contains Widevine DRM
Date: Wed, 20 Feb 2019 18:43:17 -0800	[thread overview]
Message-ID: <1550716997.3891.12.camel@jxself.org> (raw)
In-Reply-To: <87wolumspw.fsf@fastmail.com>

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

Marius Bakke wrote:
> not present in the Guix source.

Please keep in mind I was discussing upstream Chromium in that piece.
It's also not an exhaustive list.

> I cannot find these images: grepping for CC-BY-NC-SA or 'Creative
> Commons' did not aid.  Did you record the absolute paths to these
> files?

Of course - FOSSology records everything as it recursively unpacks and
searches files, metadata of files, etc. 

1.
third_party/blink/web_tests/fast/backgrounds/size/resources/SquirrelFis
h.svg has within it:
<a rel="cc:attributionURL" href="http://www.flickr.com/photos/goopymart
/">http://www.flickr.com/photos/goopymart/</a>; / <a rel="license"
href="http://creativecommons.org/licenses/by-nc-sa/2.0/">CC BY-NC-SA
2.0</a></div>

2. chrome/test/data/extensions/api_test/wallpaper_manager/test_bad.jpg
contains:
xmpRights:WebStatement="http://creativecommons.org/licenses/by-nc-sa/2.
0/

3. chrome/test/data/extensions/test.jpg contains within it:
http://creativecommons.org/licenses/by-nc-sa/2.0/

4. chrome/test/data/extensions/api_test/wallpaper/test.jpg
Identified by FOSSology as being identical to file 3.

5. chrome/test/data/extensions/api_test/wallpaper_manager/test.jpg
contains within it:
http://creativecommons.org/licenses/by-nc-sa/2.0/

> My grep-fu is really failing me today.  Where is this located?

chrome/test/data/import/firefox/macwin.zip/Profiles/brn6z0fz.default/ex
tensions/{3112ca9c-de6d-4884-a869-9855de68056c}/chrome/google-
toolbar.jar

chrome/test/data/import/firefox/macwin.zip/Profiles/brn6z0fz.default/ex
tensions/{3112ca9c-de6d-4884-a869-9855de68056c}/LICENSE.txt

Keep in mind this was not an exhaustive report of all of upstream
Chromium 73.0.3683.45 and there is much left out. They were intended
only as examples to show freedom problems within Chromium itself.

As for the rest I guess we'll need to wait on a response from the FSF
since I seem to be receving pushback myself.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2019-02-21  2:46 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
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 [this message]
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=1550716997.3891.12.camel@jxself.org \
    --to=j@jxself.org \
    --cc=34565@debbugs.gnu.org \
    /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.