[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNU-linux-libre] [PATCH] gnu: Add ungoogled-chromium.

From: Luke
Subject: Re: [GNU-linux-libre] [PATCH] gnu: Add ungoogled-chromium.
Date: Wed, 20 Feb 2019 19:37:08 -0500
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101, Thunderbird/52.9.1

On 02/20/2019 05:10 PM, Marius Bakke wrote:
> bill-auger <address@hidden> writes:
>> On Wed, 20 Feb 2019 15:50:02 +0100 Marius wrote:
>>> That message says we are no longer using a _fork_ of
>>> Ungoogled-Chromium. Earlier revisions of the patch was pulling from
>>> my repository[0], now we use the canonical upstream repository
>>> directly:
>> but then what do you do to the upstream sources? - we all agree the
>> upstream sources are not FSDG-free - arent the ungoogled patches the
>> keystone of your liberation procedure?
> The liberation procedure is right there in the package definition:
> <>.
> This script is what creates the FSDG-free source tarball presented to
> users when they run `guix build --source ungoogled-chromium`.
>> that is entirely why i am confused now - it would help tremendously if
>> you could tell us what you did to the upstream sources that you believe
>> makes the FSDG-free - like a liberation recipe in plain english would
>> be awseome
> There are comments in the script.  Please ask if any of the steps are
> unclear!  Improvements welcome.

Correct me if I'm wrong, but Widevine DRM and the ability to run
proprietary codecs is still being built according to the provided
package source?
That's definitely a blocker.

While completely removing the DRM ability and creating a clean source
tarball is optimal, it should at minimum be disabled at compile time to
protect users.

Some GN prefs missing from chromium.scm:
;; Disable non-free codecs

;; Disable DRM

;; Not XMPP compliant, walled-garden SaaSS:

;; Note:

Cleaning these modules properly would involve patching them out
completely and providing the cleaned tarball for end-users to compile.
Ungoogled-Chromium does remove the majority of Google SaaSS during the
patch process, but does not currently try to reach FSF compliance by
removing any of these proprietary anti-features or providing a cleaned

Additionally, the patches are expected to be ran against specific
Chromium releases. Future releases of Chromium are not patched/audited
yet by the ungoogled-chromium project and may leak to Google.

The Guix package is building against Chromium 72.0.3626.109 whereas the
latest release of Ungoogled-Chromium as of this moment is for

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]