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

Closed (moved)
Open
Opened Jan 24, 2018 by alecmuffett@alecmuffett

SingleOnion (and Tor2web?) connections may need better expiry, lots left open

This is a followup to #24991 (moved), which has two of the config files (tor config, and tor log)

Expanding on the description in #24991 (moved), my blog has a low traffic single onion - barely gets hit over Tor at all - yet when I investigated it recently I found it claiming to have 6 circuits open for an extended period (days) and also ~50 simultaneous TCP connections.

I confirmed this with netstat, and then by killing the Tor daemon which threw all the connections into simultaneous TIME_WAIT.

I mentioned this to Teor on IRC, who suggested that I log " a ticket about expiring single onion and tor2web connections, please" - because this seems really strange, and suggests that SingleOnions are not garbage-collecting properly.

To upload designs, you'll need to enable LFS and have 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#24992