Anti-fingerprinting and tracking protection break tinymce.com embeds
Categories
(Core :: Privacy: Anti-Tracking, defect)
Tracking
()
People
(Reporter: francois, Assigned: englehardt)
References
(Blocks 2 open bugs)
Details
Now that tinymce.com is blocked by Disconnect:
https://github.com/disconnectme/disconnect-tracking-protection/blob/master/descriptions.md#TinyCloud
any site which embeds their HTML editor will have that functionality broken.
Here's a test page which demonstrates the problem:
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 1•6 years ago
|
||
This domain is on both the analytics list and the fingerprinting base list, meaning it will also be broken with tracking protection.
Comment 2•6 years ago
|
||
This is very bad. Tinymce is a very heavily-used library.
Reporter | ||
Comment 3•6 years ago
|
||
It is widely used from a self-hosted standpoint, but I wonder how popular this hosted service is.
Also, they're sending the output of fingerprintjs2 back to their server: https://github.com/disconnectme/disconnect-tracking-protection/blob/master/descriptions.md#TinyCloud
so they definitely belong in this category.
Comment 4•6 years ago
|
||
(In reply to François Marier [:francois] from comment #3)
It is widely used from a self-hosted standpoint, but I wonder how popular this hosted service is.
Yeah, me too. At least 1500 sites turn up with a quick and dirty search here: https://publicwww.com/websites/%22cloud.tinymce.com%22/ but none of them are super popular...
Also, they're sending the output of fingerprintjs2 back to their server: https://github.com/disconnectme/disconnect-tracking-protection/blob/master/descriptions.md#TinyCloud
so they definitely belong in this category.
No doubt about that, but I wonder if we can employ a more careful scalpel here. Are we trying to prevent the JS code to compute a fingerprint, or to prevent the transmission of this fingerprint to the remote server? Given the fact that fmarier.github.io doesn't leave a cookie jar in my browser we can be sure that the identifier isn't stored locally. The identifier for me is sent to this URL:
I wonder if we can suggest to Disconnect to only put sp.tinymce.com on the analytics/fingerprinting list and leave the rest of tinymce.com alone? Is that a good way to address this?
Reporter | ||
Comment 5•6 years ago
|
||
Alternatively, could we reach out to TinyMCE to ask them why they're doing this?
Comment 7•6 years ago
|
||
just x-posted a issue on the tinymce github repository:
Assignee | ||
Comment 8•6 years ago
|
||
(In reply to :Ehsan Akhgari from comment #4)
I wonder if we can suggest to Disconnect to only put sp.tinymce.com on the analytics/fingerprinting list and leave the rest of tinymce.com alone? Is that a good way to address this?
This is an option. Disconnect has added endpoint domains to their list when the fingerprinting script is served from a CDN. Do we know if the sp.tinymce.com
domain is used for any other than as a tracking endpoint?
Comment 9•6 years ago
|
||
(In reply to Steven Englehardt [:englehardt] from comment #8)
(In reply to :Ehsan Akhgari from comment #4)
I wonder if we can suggest to Disconnect to only put sp.tinymce.com on the analytics/fingerprinting list and leave the rest of tinymce.com alone? Is that a good way to address this?
This is an option. Disconnect has added endpoint domains to their list when the fingerprinting script is served from a CDN. Do we know if the
sp.tinymce.com
domain is used for any other than as a tracking endpoint?
I don't have that info.
Comment 10•6 years ago
|
||
We will be removing the fingerprint js from our cloud shortly, it is used to track usage of our premium cloud offerings, but we will change the metrics used for that.
Comment 11•6 years ago
|
||
(In reply to joakim.lindkvist from comment #10)
We will be removing the fingerprint js from our cloud shortly, it is used to track usage of our premium cloud offerings, but we will change the metrics used for that.
Thanks a lot for getting in touch and confirming this!
Assignee | ||
Comment 12•6 years ago
|
||
(In reply to joakim.lindkvist from comment #10)
We will be removing the fingerprint js from our cloud shortly, it is used to track usage of our premium cloud offerings, but we will change the metrics used for that.
Please follow-up on this bug once you're ready and we'll forward the info to Disconnect. Thanks again for getting in touch.
Comment 13•6 years ago
|
||
The fp2 js payload is removed from all scripts loaded from our CDN/Cloud and the fp value is hard coded to "none".
Will you fwd this to Disconnect.me or should we approach them?
Updated•6 years ago
|
Assignee | ||
Comment 14•6 years ago
|
||
Thanks for the quick update! I filed https://github.com/disconnectme/disconnect-tracking-protection/issues/76 to request a re-review with Disconnect. I'll keep this open for now until we merge their list changes.
Assignee | ||
Updated•6 years ago
|
Comment 17•6 years ago
|
||
(In reply to Steven Englehardt [:englehardt] from comment #14)
I'll keep this open for now until we merge their list changes.
Sorry to bother you, but nearly a month has gone by and two duplicates have been filed in the last few days.
Assignee | ||
Comment 18•6 years ago
|
||
Fixed in https://github.com/mozilla-services/shavar-prod-lists/pull/65. I verified the Fix using Francois' test page.
Assignee | ||
Updated•6 years ago
|
Description
•