Bug#739626: How to name the websocket PT server in Debian; was ITP: tor-pt-websocket -- WebSocket pluggable transport

[Ximin Luo <infinity0@pwned.gg>]

+tor-dev and some relevant people, please keep CC

Hey all, I'd like some advice on the naming of this package.

I have some options in mind:

- flashproxy-server: The main practical use of this package is with the flashproxy[1][2] system. However, as noted in the package description, it could be used in other situations outside of flashproxy. Importantly, the code and functionality does not know about rest of the flashproxy system; as far as it is concerned, it is a "plain" Tor pluggable transport, in the sense that it "only" implements a stream-transformation in the same way as e.g. obfsproxy does, without the complexity involving addresses that (the other parts of) flashproxy provides.

- tor-pt-websocket or pt-websocket: These are unambigious but inconsistent with the other Tor pluggable transport in Debian, obfsproxy. And there is also "fteproxy"[3] which will probably retain this naming when added to Debian in the future.

- wsproxy-server: short and unambigious, consistent with "obfsproxy" and "fteproxy", but upstream has not adopted this naming. (We do not have a general convention for naming Pluggable Transports, but several others have been called *proxy, e.g. sshproxy[4] and aforementioned[3].)

X

[1] http://crypto.stanford.edu/flashproxy
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721845
[3] http://fteproxy.org/
[4] https://github.com/Yawning/sshproxy

On 20/02/14 15:42, Ximin Luo wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Ximin Luo <infinity0@pwned.gg>
> 
> * Package name    : tor-pt-websocket
>   Version         : 0~git20140130
>   Upstream Author : David Fifield <david@bamsoftware.com>
> * URL             : https://gitweb.torproject.org/pluggable-transports/websocket.git
> * License         : CC0
>   Programming Lang: Go
>   Description     : WebSocket pluggable transport - server
> 
> Pluggable transports are tools that transform a stream of application traffic
> into a different format on the network. This helps to bypass network-level
> censorship.
> 
> This package contains a server transport plugin that accepts connections
> transformed to look like the websocket protocol. This is typically used to
> enhance systems like Tor, to provide service even to censored users.
> 
> See flashproxy-client for a corresponding client transport plugin, meant for
> users to bypass censorship, that is compatible with the websocket protocol that
> this package expects.
> 
> (The source package also contains a websocket-client transport plugin, but
> this is just a demo that is less effective than flashproxy-client, and not
> meant to be used in real situations.)
> 

-- 
GPG: 4096R/1318EFAC5FBBDBCE
git://github.com/infinity0/pubkeys.git