[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #30733 [Core Tor/sbws]: sbws does not detect changes in descriptor bandwidth values
#30733: sbws does not detect changes in descriptor bandwidth values
-----------------------------------+-----------------------------------
Reporter: starlight | Owner: (none)
Type: defect | Status: needs_review
Priority: Very High | Milestone: sbws: 1.1.x-final
Component: Core Tor/sbws | Version: sbws: 1.1.0
Severity: Critical | Resolution:
Keywords: sbws-majority-blocker | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-----------------------------------+-----------------------------------
Comment (by juga):
Replying to [comment:17 starlight]:
> perhaps it would be best to not rely on scanning client instances for
descriptor information and either a) run a low-limit relay with DirCache=1
This is the default
> along with Fetch* settings expressly for providing descriptors
This is what i said in
https://trac.torproject.org/projects/tor/ticket/30733?replyto=17#comment:14.
However i don't understand what you mean by "client instances", this
configuration affects the sbws' "client instance" to which communicates
via socket.
> or b) connect directly to authorities or fallback directories when
obtaining descriptors
I considered this time ago
(https://github.com/torproject/sbws/blob/master/sbws/lib/relaylist.py#L400),
but i'm avoiding to do any request not via the Tor network, and stem's
`remote` do that.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30733#comment:19>
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