[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #7903 [Pluggable transport]: Research ways of adding Extended ORPort support to pyptlib
#7903: Research ways of adding Extended ORPort support to pyptlib
---------------------------------+------------------------------------------
Reporter: asn | Owner: asn
Type: task | Status: new
Priority: normal | Milestone:
Component: Pluggable transport | Version:
Keywords: | Parent:
Points: | Actualpoints:
---------------------------------+------------------------------------------
Comment(by dcf):
tor-dev thread: https://lists.torproject.org/pipermail/tor-
dev/2013-January/004373.html
Check #7620 for my independent implementation of extended OR support in
Go. Unfortunately it maybe doesn't help you much because there's really
only one way to implement it that makes sense in Go: as blocking network
operations on a plain socket, with the expectation that you will be called
inside an independent goroutine (thread).
Source code:
https://gitweb.torproject.org/user/dcf/flashproxy.git/tree/refs/heads/extor
:/websocket-transport
The main abstraction is the function `PtConnectOr`. It takes that
`PtServerInfo` struct that results for PT env parsing, and connects to the
regular OR port or the extended OR port as appropriate. When it connects
to the extended OR port, it does the authentication and USERADDR things
just like pyobfsproxy does.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7903#comment:1>
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