I'm interested in writing a pluggable transport for Tor. Is this spec a good place to start?
https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/180-pluggable...
Cheers, Ox
-----------------------------------------------------------------------------------------
"I love people who harness themselves, an ox to a heavy cart, who pull like water buffalo, with massive patience, who strain in the mud and the muck to move things forward, who do what has to be done, again and again."
- Marge Piercy
On Wed, Jan 29, 2014 at 03:24:51PM -0600, Ox Cart wrote:
I'm interested in writing a pluggable transport for Tor. Is this spec a good place to start?
https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/180-pluggable...
Better than proposal 180 is pt-spec.txt, which is more up to date. https://gitweb.torproject.org/torspec.git/blob/HEAD:/pt-spec.txt
For the extended OR port on the server side, see https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/196-transport... https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/217-ext-orpor... (But ignore the TransportControlPort part of proposal 196, as that's not implemented.) For the extended OR port, you may also want to look at some existing source code: https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/blob/b88efc... https://gitweb.torproject.org/pluggable-transports/goptlib.git/blob/abeea884...
David Fifield
Thanks very much David, that's exactly what I needed!
The pluggable transports page on the website still points at the old 180 proposal. Do you know whom I should ping to get that updated to point at pt-spec.txt?
Cheers, Ox
-----------------------------------------------------------------------------------------
"I love people who harness themselves, an ox to a heavy cart, who pull like water buffalo, with massive patience, who strain in the mud and the muck to move things forward, who do what has to be done, again and again."
- Marge Piercy
On Wed, Jan 29, 2014 at 6:19 PM, David Fifield david@bamsoftware.comwrote:
On Wed, Jan 29, 2014 at 03:24:51PM -0600, Ox Cart wrote:
I'm interested in writing a pluggable transport for Tor. Is this spec a
good
place to start?
https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/180-pluggable...
Better than proposal 180 is pt-spec.txt, which is more up to date. https://gitweb.torproject.org/torspec.git/blob/HEAD:/pt-spec.txt
For the extended OR port on the server side, see
https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/196-transport...
https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/217-ext-orpor... (But ignore the TransportControlPort part of proposal 196, as that's not implemented.) For the extended OR port, you may also want to look at some existing source code:
https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/blob/b88efc...
https://gitweb.torproject.org/pluggable-transports/goptlib.git/blob/abeea884...
David Fifield
On Wed, Jan 29, 2014 at 08:42:05PM -0600, Ox Cart wrote:
Thanks very much David, that's exactly what I needed!
The pluggable transports page on the website still points at the old 180 proposal. Do you know whom I should ping to get that updated to point at pt-spec.txt?
Fixed.
(Let us know if there are other things that need fixing too.)
Thanks! --Roger
That was quick! Thanks Roger.
Cheers, Ox
-----------------------------------------------------------------------------------------
"I love people who harness themselves, an ox to a heavy cart, who pull like water buffalo, with massive patience, who strain in the mud and the muck to move things forward, who do what has to be done, again and again."
- Marge Piercy
On Wed, Jan 29, 2014 at 8:45 PM, Roger Dingledine arma@mit.edu wrote:
On Wed, Jan 29, 2014 at 08:42:05PM -0600, Ox Cart wrote:
Thanks very much David, that's exactly what I needed!
The pluggable transports page on the website still points at the old 180 proposal. Do you know whom I should ping to get that updated to point at pt-spec.txt?
Fixed.
(Let us know if there are other things that need fixing too.)
Thanks! --Roger
tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
I think a good place to start would be to use the obfsproxy python api... but of course you could create a PT without this api.
Here the unofficial tor PT wiki page: https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports
Here you can look at example code of various PTs. Some use the python obfsproxy api and some don't.
On Wed, Jan 29, 2014 at 9:24 PM, Ox Cart ox@getlantern.org wrote:
I'm interested in writing a pluggable transport for Tor. Is this spec a good place to start?
https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/180-pluggable...
Cheers, Ox
"I love people who harness themselves, an ox to a heavy cart, who pull like water buffalo, with massive patience, who strain in the mud and the muck to move things forward, who do what has to be done, again and again."
- Marge Piercy
tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev