[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: needs_review
Priority: Medium | Milestone:
Component: Core Tor/Stem | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: atagar | Sponsor:
---------------------------+------------------------------
Changes (by dmr):
* status: assigned => needs_review
Comment:
Replying to [comment:4 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.)
I think it's a safe assumption for me that this is a good change :).
Without knowing more about reachability testing, I'd imagine it
constitutes some sort of outbound communication to check whether our
ORPort is reachable from another relay. Since we explicitly don't want to
publish info to contact our relay, turning off this sort of behavior just
makes sense to me (if it //is// as I'm guessing it to be).
I've pushed another commit to the github branch:
`git@xxxxxxxxxx:dmr-x/stem.git` branch `25631-integ-torrc` commit
`37d11c67773361bbebf521691d57468e6ea51d32`
web links:
https://github.com/dmr-x/stem/tree/25631-integ-torrc
https://github.com/dmr-x/stem/commit/37d11c67773361bbebf521691d57468e6ea51d32
atagar and/or teor: please review :)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25631#comment:6>
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