[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #9652 [BridgeDB]: Treat Pluggable Transports as Individual Bridges
#9652: Treat Pluggable Transports as Individual Bridges
-----------------------------+---------------------------------------
Reporter: sysrqb | Owner:
Type: enhancement | Status: closed
Priority: normal | Milestone:
Component: BridgeDB | Version:
Resolution: not a bug | Keywords: bridgedb-dist, tor-bridge
Actual Points: | Parent ID:
Points: |
-----------------------------+---------------------------------------
Changes (by isis):
* status: new => closed
* keywords: => bridgedb-dist, tor-bridge
* resolution: => not a bug
Comment:
Just to make sure I'm interpreting this correctly:
We currently have a hashring for each distributor, then an extra pseudo-
hashring for buckets. Each hashring is subdivided into subhashrings
according to filters (which would include filters for PT type, IPv4/6,
etc.), and/or the client's IP address /24, and/or other parameters. These
subhashrings are cached (or at least some number N of them are).
If you get a bridge's fingerprint, you get the bridge's `@type bridge-
server-descriptor`. Even though my local tor client is configured to
download extra-info descriptors, I've never been able to get the control
port to spit out an `@type bridge-extrainfo-document` with `GETINFO extra-
info/digest/*` and the extra-info digest from the `@type bridge-server-
descriptor`. '''tl;dr''': Given one PT `type IP:port`, I don't ''think''
you can get the other PT `types IP:port`s; however, given the fingerprint
you can get the main `ORPort` of the bridge.
We can't really keep that separate without making changes to little-t tor,
and probably redesigning large portions of how the `ExtORPort` functions.
I'm not really sure what to do for this ticket, unless I'm
misunderstanding something.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9652#comment:6>
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