Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Use data-sha1 attribute to compare scripts, css, etc. avoiding the need for CDNs that track

  • 2 balasan
  • 1 ada masalah ini
  • 3 paparan
  • Balasan terakhir oleh AliceWonder

Hi, I would like to see an attribute added to FireFox (and every browser) to decrease tracking.

When webmasters use a public CDN (e.g. scripts.google.com or wherever) for things like jQuery etc., they are potentially opening up their users to tracking by those CDNs.

If we had a data-sha1 attribute that could contain the sha1sum of the script we are referencing, it could improve security and privacy in two ways:

A) Prevent cases where the CDN has been compromised altering the resource being referenced, because then the checksum won't match.

B) If the browser already has a script cached with a matching checksum, then it doesn't need to fetch it from any CDN or server etc. or even ask if the version it has is current. If the checksum of a resource in cache matches, then it is the same file regardless of where it came from and the browser does not need to send any headers to anyone.

Okay, the possibility of collisions exist even though the odds are astronomically low, so maybe verify the filename matches too.

Hi, I would like to see an attribute added to FireFox (and every browser) to decrease tracking. When webmasters use a public CDN (e.g. scripts.google.com or wherever) for things like jQuery etc., they are potentially opening up their users to tracking by those CDNs. If we had a data-sha1 attribute that could contain the sha1sum of the script we are referencing, it could improve security and privacy in two ways: A) Prevent cases where the CDN has been compromised altering the resource being referenced, because then the checksum won't match. B) If the browser already has a script cached with a matching checksum, then it doesn't need to fetch it from any CDN or server etc. or even ask if the version it has is current. If the checksum of a resource in cache matches, then it is the same file regardless of where it came from and the browser does not need to send any headers to anyone. Okay, the possibility of collisions exist even though the odds are astronomically low, so maybe verify the filename matches too.

All Replies (2)

Suggestions to improve Firefox can be submitted here: https://input.mozilla.org/en-US/feedback

Or a Bug report can be filed. https://bugzilla.mozilla.org/

https://developer.mozilla.org/en/Bug_writing_guidelines

Their feedback seems to be about existing features as the interface wants to know what made me happy or sad, and this is a request - not feedback on what made me happy or sad.

It's also not a bug.