[Top][All Lists]

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

Re: [GNU-linux-libre] DSFG in perpetuity

From: Luke
Subject: Re: [GNU-linux-libre] DSFG in perpetuity
Date: Mon, 2 Apr 2018 18:53:25 -0400
User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101, Thunderbird/52.2.1

On 04/01/2018 11:13 PM, Isaac David wrote:
> LukeĀ  wrote :
>> Users should be aware that QTWebengine is based on Chromium and
>> therefore contains many of the same flaws.
> This assertion in particular raises some alarms. I don't
> think that was ever established to be the case; and
> insofar as the suspicion goes, both KDE and Qt developers
> denied it[1][2] and even updated their documentation in
> accordance to our concerns[3].
> Is your view still that Qt Webengine poses a problem to
> free distros, and if so, why?

When I asked their development team whether or not they use
ungoogled-chromium patches, they continued to say those patches do not
apply to them as they used a "stripped down version".
(e.g. they delete large parts of the /browser and /ui directories) I
haven't done extensive review, but as of the date of the e-mail there
was still some freedom issues and plenty of links to which
could still be stripped out.

List of good patches:

Compare to QTWebengine's (outdated) Chromium:

Among the issues that stuck out to me were...
- WideVine DRM support.
- Debian freedom patches not applied, e.g. files missing licenses:
- There may still be connections made to Google API.

Having the /browser folder removed is certainly a good start, I'm just
not convinced they completely resolved it in their fork. So far
ungoogled-chromium is the only project I've compiled and ran with
Wireshark that did not have random connections to while the
browser is idling.

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

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