Opened 3 years ago

Last modified 3 years ago

#21990 new enhancement

Use a sensible default set of bandwidth servers

Reported by: teor Owned by:
Priority: Medium Milestone:
Component: Core Tor/Torflow Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: #24499 Points:
Reviewer: Sponsor:


The default bandwidth authority HTTPS server is easy to overload by mistake, and has no redundancy.

Ideally, we should specify a default list with:

  • An IPv4 address,
  • An IPv6 address,
  • A DNS address (ideally on a CDN with dual-stack support)
  • An onion address (once we test this works)

Child Tickets

#24090defectnewtomRemove default bwserver

Change History (7)

comment:1 Changed 3 years ago by arma

weasel and micah put the bwauth files on our fastly cdn server. That's worth checking out.

comment:2 Changed 3 years ago by teor

Priorities and Severities in torflow are meaningless, setting them all to Medium/Normal.

comment:3 Changed 3 years ago by teor

Owner: aagbsn deleted
Status: newassigned

aagbsn was the default owner, unassigning

comment:4 Changed 3 years ago by teor

Parent ID: #24499

comment:5 Changed 3 years ago by teor

Status: assignednew

Mark all tickets that are assigned to nobody as "new".

comment:6 Changed 3 years ago by mikeperry

Hrmm. I think that this ticket (and its child) should be dupped to #24674, which is a more specific and well-reasoned plan.

comment:7 Changed 3 years ago by teor

This ticket is about the default bandwidth servers we put in the code, rather than the ones used by the public network bandwidth authorities.

I'm not sure if how much we gain by trying to keep them secret, but some (bandwidth) authority operators have chosen to do so.

I would hate to derail #24674 by making the set of bandwidth servers shared and public at the same time.

Note: See TracTickets for help on using tickets.