Opened 2 years ago

Closed 8 months ago

#20192 closed enhancement (wontfix)

When outputting potential new fallbacks, blacklist the whitelist

Reported by: teor Owned by: haxxpop
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Fallback Scripts Version:
Severity: Normal Keywords: fallback
Cc: Actual Points:
Parent ID: Points: 0.5
Reviewer: Sponsor:

Description

When we look for potential new fallback directory mirrors, we want to ignore existing whitelisted fallbacks, as well as the blacklist.

Child Tickets

Change History (7)

comment:1 Changed 2 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:2 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:3 Changed 2 years ago by haxxpop

Owner: set to haxxpop
Status: newassigned

comment:4 Changed 19 months ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:5 Changed 18 months ago by nickm

Component: Core Tor/TorCore Tor/Fallback Scripts

comment:6 Changed 12 months ago by teor

This is the old wiki text:

We want to only find new potential fallbacks, and ask their operators to opt-in. So we add both lists together, and tell the script not to select anything in those lists. (All those operators have already been contacted, and responded.)

  1. Make sure the whitelist is the current one from git master (not the modified one from step 1)
  2. Make sure the blacklist is saved in a git branch or a backup
  3. Append the whitelist to the blacklist
    cat scripts/maint/fallback.whitelist >> scripts/maint/fallback.blacklist
    
  4. Set the log level to INFO for both the script and stem:
    - logging.basicConfig(level=logging.WARNING)
    + logging.basicConfig(level=logging.INFO)
    
    - logging.getLogger('stem').setLevel(logging.WARNING)
    + logging.getLogger('stem').setLevel(logging.INFO)
    
  5. Output candidate fallbacks (ignore the whitelist, log operator contact details):
    - OUTPUT_CANDIDATES = False
    + OUTPUT_CANDIDATES = True
    
  6. Run the fallback selection script, saving the list:
    scripts/maint/updateFallbackDirs.py > potential_extra_fallbacks 2> potential_extra_fallbacks.log
    

This can take a long time, as it downloads ~150MB of OnionOO data, parses it, then tries each fallback's DirPort.

comment:7 Changed 8 months ago by teor

Resolution: wontfix
Status: assignedclosed

We don't plan on contacting operators individually any more.

Note: See TracTickets for help on using tickets.