Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
decentraleyes
decentraleyes
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 84
    • Issues 84
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards

Microsoft has acquired GitHub. Decentraleyes has left GitHub. Welcome to its new home!

To participate, please register, or sign in with an existing GitLab.com, Bitbucket, or GitHub account.

Past contributions on GitHub? Be sure to reclaim your Comments, Issues, and Pull Requests.

  • Thomas Rientjes
  • decentraleyesdecentraleyes
  • Issues
  • #188

Closed
Open
Opened Aug 23, 2017 by Thomas Rientjes@SynzvatoMaintainer

Network prediction features cause request leakage

First off, many thanks to @Bisaloo for testing beta1 of the WebExtension under uncommon conditions, and for finding and reporting this issue. It's great to see that the beta is being thoroughly tested!

Currently affected users

This issue affects early adopters of the beta for Firefox who have network prediction set to enabled, and are not using content blockers (e.g. uBlock Origin) that automatically disable this feature by default.

General problem description

Despite the fact that Decentraleyes properly redirects requests away from large CDNs, some settings cause browsers to attempt to predict your network traffic, and send requests out before noticing that the request is not supposed to occur. This feature can cause unnecessary request leakage.

Resolving the issue

You can fix the issue by rebuilding, and reinstalling Decentraleyes from the very latest commit inside of the master branch (7d21a1ed). The upcoming, packaged, release of beta1 will ship with the fix.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: Synzvato/decentraleyes#188