Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #33648

Closed (moved)
(moved)
Open
Created Mar 18, 2020 by cypherpunks@cypherpunks

vanguards: What is the recommended value?

Since your default configuration & github document doesn't tell me much, I'd like to hear developer's opinion on this.

vanguards.conf

Bandguards: circ_max_age_hours = 1 (Mine is just simple WWW service without fancy WebSockets, downloads or videos) circ_max_hsdesc_kilobytes = 30 circ_max_megabytes = 5

Q1. Is using smaller value such as 1 for circ_max_age_hours have any problems regarding anonymity?

Q2. You didn't mention default size of hidden service descriptor. What value is it? This is not OnionShare or onionbalance. (if you can do {circ_max_hsdesc_kilobytes != normal_desc_size kill_connection} that's great)

Q3. You said "HTTP GET can resume if this limit is hit, HTTP POST will not" in circ_max_megabytes. You better add this text, don't you think: "If the client reach this limit, we close the connection and create another one to continue operation. Client will experience small downtime."

Q4. Can you add an option to slow down packets on purpose, to prevent simple DDoS? e.g. 'limit_packets_per_seconds = 10' will allow 10 packets per seconds and delay exceeded packets (x) seconds

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking