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

Re: [tor-bugs] #31252 [Circumvention/BridgeDB]: Equip BridgeDB with anti-bot mechanism

#31252: Equip BridgeDB with anti-bot mechanism
------------------------------------+-----------------------------
 Reporter:  phw                     |          Owner:  phw
     Type:  enhancement             |         Status:  merge_ready
 Priority:  Medium                  |      Milestone:
Component:  Circumvention/BridgeDB  |        Version:
 Severity:  Normal                  |     Resolution:
 Keywords:                          |  Actual Points:
Parent ID:                          |         Points:  4
 Reviewer:  cohosh                  |        Sponsor:
------------------------------------+-----------------------------
Changes (by cohosh):

 * status:  needs_review => merge_ready


Comment:

 This looks good to me. Do we need to add this to the
 [https://gitweb.torproject.org/torspec.git/tree/bridgedb-spec.txt
 specification]?

 I'm interested in how the decisions on what headers to blacklist will be
 made. Since the files are meant to not be public, is there some process we
 go through to add new things to the blacklist or ensure that we're not
 introducing too many false positives here?

 The idea of giving out a decoy bridge is very nice. It would be
 interesting to see where/when this bridge gets blocked.

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