Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #18702

Closed
Open
Opened Apr 01, 2016 by cypherpunks@cypherpunks

Downloaded files integrity

Malicious exit nodes can modify downloaded files in the way they will cause malicious activity. For example, they can add malware to executables or embed exploit into PDFs. Most of binaries in the Web are non-signed and downloaded via http. Even if they were signed, there is no way for a Tor user to know that they were signed prior malicious modification removing any trace of a signature.

So we need a bot downloading different binaries via different exit nodes and non-torified connections, comparing the results and blacklisting malicious exit nodes.

Naive implementation is vulnerable to the attack: a malicious website can give a randomized binary to victim exit nodes causing them to be blacklisted. Malicious CDNs or NSA hardware in main ISPs can be much more dangerous and stealthy.

Maybe we should ship a db of hashes of popular binaries (programs, pdfs, etc) and check their integrity?

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: legacy/trac#18702