[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: Tue, 3 Apr 2018 19:18:20 -0400
User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101, Thunderbird/52.2.1

On 04/03/2018 04:40 PM, Isaac David wrote:
> I was about to say that, although worrisome, spyware capabilities
> have no impact in determining whether a piece of software belongs
> in a FSDG distro or not. Good thing I double-checked with the
> guidelines, because they actually do.
Yes, per: "The distro must contain no DRM, no back doors, and no spyware."
> Luke wrote :
>> [A]s 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:
> This doesn't tell us much unfortunately.

The patches mention various places where Google API and pre-compiled
binaries are being removed, obviously QT is 4 years behind the latest
patches which makes it more difficult to do a 1:1 comparison.
I would say many of the issues are resolved due to their scrubbing.

>> - Debian freedom patches not applied, e.g. files missing licenses:
> What does that mean exactly? If I were to guess, lintian incorrectly
> confused trace_data.js for a blob, and ungoogled-chromium is reversing
> that overstep.

Yes, it was presumed to be a blob by Debian (and it is currently missing
license header)

>> - There may still be connections made to Google API.
>> 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.
> By *the only project* do you mean you also tested with Qt
> Webengine-based programs? Conclusions about Chromium need
> not apply to Qt Webengine.
Of the projects I've tested: Ungoogled-chromium - no google connections
found presently, Inox - Leaks google account data on settings page
(fixed in recent commit)
I have not used QTWebengine in over a year and never ran a leak test. -
If someone has the time to do this and verify there are no freedom
issues, they can be removed from the conclusion as you mentioned.

reply via email to

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