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

Closed (moved)
Open
Opened Jul 11, 2014 by George Kadianakis@asn

Save retrieved bridge information in our state file

Currently, Tor clients don't remember anything about bridges after a restart. So for example, if there was a torrc Bridge line without a fingerprint specified, and Tor retrieves the fingerprint from the descriptor, it won't save it on the disk.

Or, if a bridge changed IP:PORT, but we managed to get its new ip:port using the bridge authority (see #12599 (moved)), we will not save this down either.

Fortunately, Sebastian wrote proposal192 about this issue: https://gitweb.torproject.org/torspec.git/tree/proposals/192-store-bridge-information.txt

We should re-read the proposal, revise it as needed and implement it.

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