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

Closed (moved)
Open
Opened Apr 09, 2020 by cypherpunks@cypherpunks

vanguards: circ_max_megabytes applied to all connection

# This means that applications that require large data submission (eg
# SecureDrop or onionshare) should set this much higher
# (or set to 0 to disable):
circ_max_megabytes = 8

My site is less than 4MB so above config is okay.

I thought vanguards only applies this limit to:

  1. My onion service <--- Tor user (incoming)
  2. My onion service ---> Tor user (outgoing)

However your vanguards is breaking other connections such as:

  1. apt with Tor[1]
  2. wget download over Tor to clearnet site
  3. curl POST something over Tor to clearnet site

Problem 1. I don't want to stop vanguards just for apt and other thing. Problem 2. I don't want to increase circ_max value just for this.

So could you please add a switch to limit only my-onion-site related connection and ignore else?

say,

# If true, vanguards will not apply max_mega limit non-onion connections.
# If false(default) vanguards will apply max_mega limit to all Tor connections.
# If your circ_max_megabytes is already 0, this settings does nothing.
circ_max_mega_ignore_clearnet_destination = true
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#33861