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
  • #7661

Closed (moved)
Open
Opened Dec 07, 2012 by Jacob Appelbaum@ioerror

Tor Browser update security

I'm watching a user update their Tor Browser and they not only went and downloaded it, they opened the .gz, unpacked it and ran it.

I suspect it would be straightforward to have a small handler for opening Tor Browser downloads that verifies the download with a very small build of gpgv. Combined with the new Firefox cert pinning, I'd feel rather good about downloading updates as we clearly (I hope someone clarifies otherwise!) won't have Thandy anytime soon.

I imagine that it would be a nice way to ensure that there is only one leap of faith, ever. The first is unavoidable and afterwards, everything else is unnecessary.

If I wrote a patch to build/include gpgv (with our gpg keys preloaded) - would that be something we could ship? Could we easily hook it for torproject.org downloads?

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