[wp-trac] [WordPress Trac] #43492: Core Telemetry and Updates
WordPress Trac
noreply at wordpress.org
Wed Mar 7 22:33:20 UTC 2018
#43492: Core Telemetry and Updates
------------------------------+------------------------------
Reporter: xkon | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Upgrade/Install | Version:
Severity: normal | Resolution:
Keywords: gdpr 2nd-opinion | Focuses:
------------------------------+------------------------------
Changes (by danieltj):
* keywords: gdpr => gdpr 2nd-opinion
* component: General => Upgrade/Install
Comment:
I'm not a GDPR expert here by any means, but the data sent in the request
wouldn't class as personal information and as such, doesn't matter if it's
sent to WordPress.org, does it? Either way, this is integral in ensuring
that the site gets security updates (and other feature updates).
This can be somewhat remedied by disabling updates for your site, in which
case the request data doesn't need filtering because it's never sent? Or
is it sent first but the update is blocked? I haven't checked how Core
fully does updates from start to finish.
The biggest problem I see with this is a big rewrite on how updates are
performed because ideally you want to prevent an update site-side before
the data is compiled and sent to WordPress.org's API to check the request
data to see if the site is eligible for the update. This is a very tricky
issue for sure.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/43492#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list