[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #7550 [BridgeDB]: BridgeDB email responder is not interactive
#7550: BridgeDB email responder is not interactive
----------------------+-----------------------------------------------------
Reporter: aagbsn | Owner:
Type: defect | Status: needs_information
Priority: normal | Milestone:
Component: BridgeDB | Version:
Keywords: | Parent:
Points: | Actualpoints:
----------------------+-----------------------------------------------------
Comment(by aagbsn):
Replying to [comment:1 isis]:
> Replying to [ticket:7550 aagbsn]:
> > BridgeDB's email response mentions that it supports queries for ipv6
bridges and bridges with specified transports, but the rate limiting
feature prevents the responder from being used in an interactive way.
> >
> > We could modify the rate limiting feature to allow several requests
before responding negatively.
> >
> > Alternately, the first response could include a brief set of
instructions only, and only apply rate limiting to subsequent queries for
bridges. However, this might be confusing, especially if not all
translations are initially available.
>
> What if we were to do separate rate limits? Something like:
>
> 1. a stricter (less queries allowed) for the 'get bridges' command
> 2. a more permissive rate limit for all other valid commands
> 3. an eventual blocked-for-X-amount-of-time for some threshold of non-
valid commands
This is a fine strategy, though it might be easier to just relax the rate
limit to something like 5 requests per hour.
We should also consider replying with obfs2,3 bridges by default in each
mail.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7550#comment:2>
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