canmove, Confirmed users
1,537
edits
Privacy/Reviews/Telemetry: Difference between revisions
Jump to navigation
Jump to search
→User Data Risk Minimization
| Line 128: | Line 128: | ||
In this section, the privacy champion will identify areas of user data risk and recommendations for minimizing the risk. | In this section, the privacy champion will identify areas of user data risk and recommendations for minimizing the risk. | ||
=== Fingerprinting === | === Fingerprinting === | ||
| Line 139: | Line 137: | ||
''Recommendation'': If possible, the SSL certificate fingerprint should be hard coded into the client and verified before transmitting data so the client can be sure the server where it is sending data is indeed the Telemetry server (and not an attacker intercepting traffic). | ''Recommendation'': If possible, the SSL certificate fingerprint should be hard coded into the client and verified before transmitting data so the client can be sure the server where it is sending data is indeed the Telemetry server (and not an attacker intercepting traffic). | ||
{{ResolutionBox|{{resolved|Required action completed, SSL used on server and invalid certificates cause connection to drop. Recommended fingerprint-hardcoding not implemented.}} }} | |||
{{ResolutionBox|{{ | |||
= Conformity to Private Browsing Mode = | = Conformity to Private Browsing Mode = | ||