Re: [tor-bugs] #20174 [Core Tor/Fallback Scripts]: Automate checking existing fallbacks

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#20174: Automate checking existing fallbacks
-------------------------------------------------+-------------------------
 Reporter:  teor                                 |          Owner:  haxxpop
     Type:  enhancement                          |         Status:
                                                 |  merge_ready
 Priority:  Medium                               |      Milestone:  Tor:
                                                 |  0.3.0.x-final
Component:  Core Tor/Fallback Scripts            |        Version:  Tor:
                                                 |  0.2.8.1-alpha
 Severity:  Normal                               |     Resolution:
 Keywords:  fallback, tor-03-unspecified-201612  |  Actual Points:
Parent ID:                                       |         Points:  1
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------
Changes (by teor):

 * status:  needs_revision => merge_ready
 * milestone:  Tor: unspecified => Tor: 0.3.0.x-final


Old description:

> I use a manual process to check existing fallbacks. It would be great if
> the updateFallbackDirs.py script would automatically read
> src/or/fallback_dirs.inc, and check each fallback for errors.
>
> For details, see:
> https://trac.torproject.org/projects/tor/wiki/doc/UpdatingFallbackDirectoryMirrors

New description:

 I use a manual process to check existing fallbacks. It would be great if
 the updateFallbackDirs.py script would automatically read
 src/or/fallback_dirs.inc, and check each fallback for errors.

 For details, see:
 https://trac.torproject.org/projects/tor/wiki/doc/UpdatingFallbackDirectoryMirrors

 I think it can go in 0.3.0

--

Comment:

 Replying to [comment:10 haxxpop]:
 > Replying to [comment:9 teor]:
 > > The check_existing mode would be more useful if it only logged warning
 and info messages for relay fingerprints in the existing list. I have
 opened #21282 for this enhancement.
 >
 > What does "for relay fingerprints" mean?

 Each relay has a unique identifier called a "fingerprint".
 So log messages about a fingerprint for a fallback should be logged.
 Otherwise, they should be ignored.

 We can do the changes to the log messages in ticket #21282.
 There are more details in that ticket.

 > ps. I have already updated the usage message.

 Thanks, then this patch is ready to be merged, it just needs a changes
 file:
 https://gitweb.torproject.org/tor.git/tree/doc/HACKING/CodingStandards.md#n56

 {{{
 - Minor enhancements (fallback scripts):
     - Add a check_existing mode to updateFallbackDirs.py, which checks if
 fallbacks in
       the hard-coded list are working. Closes ticket 20174. Patch by
 haxxpop.
 }}}

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20174#comment:11>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs