Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
privacy_policy [2018/05/23 18:32]
cvh [Wiki]
privacy_policy [2019/06/29 04:16] (current)
chewitt [Update System]
Line 49: Line 49:
 The complete list of information passed to the update system is: The complete list of information passed to the update system is:
  
-  * SYSTEMID: ​An MD5 hash of the primary MAC address, e.geth0+  * SYSTEMID: ​Since LE 8.2, a unique identifier generated by uuidgen at install time. Before LE 8.2, an MD5 hash of the primary MAC address.
  
   * DISTRIBUTION:​ The distribution name, e.g LibreELEC   * DISTRIBUTION:​ The distribution name, e.g LibreELEC
Line 61: Line 61:
   * x64_CPU: 1 or 0 (true or false) to indicate if the system has a 64-bit capable CPU   * x64_CPU: 1 or 0 (true or false) to indicate if the system has a 64-bit capable CPU
  
-As SYSTEMID is a unique value it allows us to distinguish active systems. This is useful for the project because web download statistics and page hits do not give a clear picture on the size of our active user-base. It also allows us to create system groups. Group functionality allows us to restrict an update to a specific group of known test volunteers or boxes without forcing change to all systems. As the project grows in size it becomes more important to have this kind of selective testing capability.+As SYSTEMID is a unique value it allows us to distinguish active systems. This is useful for the project because web download statistics and page hits do not give a clear picture on the size of our active user-base. It also allows us to create system groups. Group functionality allows us to restrict an update to a specific group of known test volunteers or boxes without forcing change to all systems. As the project grows in size it becomes more important to have this kind of selective testing capability. Since LE 8.2 it is possible to opt-out of passing the SYSTEMID identifier when making the update check.
  
 The back-end database also tracks the date/time of last check (only one entry, there is no history) which allows us to determine the number of active systems in a given time range, e.g. active in the last 30 days. The update system also records the public IP address the update check was performed from. This is not visible to normal staff (only to the database admin) but can be dumped for periodic analysis (mapping) so we understand where we have geographic concentrations of users. This guides decisions on language support and where we need to recruit additional download mirrors. The back-end database also tracks the date/time of last check (only one entry, there is no history) which allows us to determine the number of active systems in a given time range, e.g. active in the last 30 days. The update system also records the public IP address the update check was performed from. This is not visible to normal staff (only to the database admin) but can be dumped for periodic analysis (mapping) so we understand where we have geographic concentrations of users. This guides decisions on language support and where we need to recruit additional download mirrors.