[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #13202 [Tor]: Figure out a way to deal with bridges missing arguments.
#13202: Figure out a way to deal with bridges missing arguments.
-------------------------+-------------------------------------------------
Reporter: yawning | Owner:
Type: defect | Status: assigned
Priority: normal | Milestone: Tor: 0.2.???
Component: Tor | Version: Tor: unspecified
Resolution: | Keywords: bridgedb-dist, scramblesuit,
Actual Points: | isis2014Q3Q4, isis2015Q1Q2
Points: | Parent ID:
-------------------------+-------------------------------------------------
Comment (by isis):
I just grepped for the contact lines for the broken bridges, and not a
single broken PT bridge has contact info. (I was going to send emails to
the operators before trashing their bridges.)
As a slight tangent, I think some of these bridges might have something
extra wonky going on; I saw bridge extrainfo descriptors like:
{{{
[â]
transport scramblesuit 1.1.1.1:1111
[â]
bridge-ip-transports scramblesuit=8
}}}
which shouldn't be possibleâ unless these `password`less scramblesuit
bridges are being used as private bridges and the operators wanted to send
us statistics? Only some minority of the `password`less scramblesuit
bridges had wonky `bridge-ip-transports` reporting scramblesuit usage
(~1:20 broken ones). At least one broken scramblesuit bridge had `bridge-
ip-transports scramblesuit=16`.
It's nice of them to send us statistics, I guess?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13202#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