[tor-bugs] #3587 [Tor Bridge]: Accounting should work with pluggable transports
Tor Bug Tracker & Wiki
torproject-admin at torproject.org
Fri Dec 9 01:23:03 UTC 2011
#3587: Accounting should work with pluggable transports
------------------------+---------------------------------------------------
Reporter: asn | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Tor: unspecified
Component: Tor Bridge | Version:
Keywords: | Parent: #3591
Points: | Actualpoints:
------------------------+---------------------------------------------------
Comment(by asn):
Replying to [comment:5 nickm]:
> > Our current answer is doing accounting and rate-limiting directly on
the pluggable transport proxy binary
>
> Yup. I think this will have to do for 0.2.3.x.
>
> > My suggestion would be to have tor using the Extended OR Port transmit
real-time accounting/rate-limiting information to the proxy. IIRC you
don't like the idea of the Extended OR Port maintaining a continuous
relationship with the proxy, and you want the Extended OR Port restricted
to carrying data after the initial negotiation.
>
> This would definitely need specification.
>
Yes.
> I think the right way to do it, if we need continuous feedback between
the plugin and Tor, is to have the Extended OR port's role here be limited
to establishing an identifier for each connection, so that Tor can tell
the plugin about connections out-of-band.
How much out-of-band are you thinking of? Do you mean an extra Tor port,
which will only be used to transfer information between Tor and the plugin
based on the identifiers negotiated through Extended OR port?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3587#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list