[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #8979 [pyobfsproxy]: obfsproxy: Use server-side transport parameters
#8979: obfsproxy: Use server-side transport parameters
-------------------------+--------------------------------------------------
Reporter: asn | Owner: asn
Type: task | Status: new
Priority: normal | Milestone:
Component: pyobfsproxy | Version:
Keywords: | Parent:
Points: | Actualpoints:
-------------------------+--------------------------------------------------
Comment(by asn):
Steps for completion of this ticket:
- Make pyptlib parse the `TOR_PT_SERVER_TRANSPORT_PARAMETERS` environment
variable (#8929), and return it to the transport. Also, make pyptlib send
the `ARGS` option in its `SMETHOD` lines.
- Make obfsproxy get the parameters from pyptlib and pass it to the
correct transport. obfsproxy currently gets info from pyptlib in
`managed/server.py` using the `managed_info` variable. That info should
somehow reach the transports (preferably in a clean way), so that
transports can configure their shared-secrets etc.
- Obfsproxy transports should be able to select some of those parameters
and send them back to tor (using the `SMETHOD` line and `ARGS`) so that
they can be sent to BridgeDB. `SMETHOD` lines are currently sent in
`managed/server.py` using the `pyptlib` `reportSuccess` function.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/8979#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