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

Re: [tor-bugs] #9264 [BridgeDB]: Problem with transport lines in BridgeDB's bridge pool assignment files

#9264: Problem with transport lines in BridgeDB's bridge pool assignment files
--------------------------+-------------------------------
     Reporter:  karsten   |      Owner:  isis
         Type:  defect    |     Status:  needs_information
     Priority:  major     |  Milestone:
    Component:  BridgeDB  |    Version:
   Resolution:            |   Keywords:
Actual Points:            |  Parent ID:
       Points:            |
--------------------------+-------------------------------

Comment (by sysrqb):

 possible breakthrough on this by isis. Overall, this issue appears to have
 become worse over the last few months but due to the workaround we
 implemented it wasn't noticable. It appears that tonga is including old
 bridge descriptors in the file it sends us, as many as 4 from last 24
 hours it seems.

 To get an idea, here are the number of bridges descriptors sent by tonga
 and unique bridges contained within that set. Also included is a slightly-
 nasty command to check this.
 {{{
 $ grep -c fingerprint bridge-descriptors
 11588
 $ grep fingerprint bridge-descriptors | sort -u | wc -l
 4300

 $ grep -A 1 ^published bridge-descriptors | sed -e 's/opt //g' -e
 's/fingerprint/ fingerprint /g' | tr -d '\n' | sed 's/\-\-/\n/g' | sort -k
 4 | less
 }}}

 So, next stop bridge auth.

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