[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #25631 [Core Tor/Stem]: Integration tests set up and publish descriptors for an exit relay

#25631: Integration tests set up and publish descriptors for an exit relay
---------------------------+--------------------------
 Reporter:  dmr            |          Owner:  dmr
     Type:  defect         |         Status:  assigned
 Priority:  Medium         |      Milestone:
Component:  Core Tor/Stem  |        Version:
 Severity:  Normal         |     Resolution:
 Keywords:                 |  Actual Points:
Parent ID:                 |         Points:
 Reviewer:  atagar         |        Sponsor:
---------------------------+--------------------------

Comment (by dmr):

 teor:
 I don't fully get the `AssumeReachable` option.
 I'm running `Tor 0.3.2.10 (git-0edaa32732ec8930)` and this is what my `man
 torrc` says:

 {{{
 AssumeReachable 0|1
     This option is used when bootstrapping a new Tor network. If set to 1,
 don’t do self-reachability
     testing; just upload your server descriptor immediately. If
 AuthoritativeDirectory is also set, this
     option instructs the dirserver to bypass remote reachability testing
 too and list all connected
     servers as running.
 }}}

 I'm assuming that the part about `just upload your server descriptor
 immediately` is moot with `PublishServerDescriptor 0`, although that's not
 quite clear from the manual. So I'm assuming the combo means `don’t do
 self-reachability testing`, which //does// sound quite appropriate for a
 local test relay, although I'm not sure what reachability testing looks
 like. (Just thought I'd ping you for confirmation and a potential learning
 opportunity for me.)


 `ProtocolWarnings 1`, `SafeLogging 0`, and `LogTimeGranularity 1` all look
 good; I'll file that as another trac ticket just because I feel they
 constitute an enhancement, not a defect. :)

 `SOCKSPort 0` doesn't make sense - at least //not right now//. There's
 only a chief torrc used as the base for integration tests in stem, many of
 which rely on the SocksPort.

 I would agree that it makes sense in the future to split this up into
 multiple torrc sets for different tests.

 Thanks again for the feedback! :)

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25631#comment:4>
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