[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #7167 [Pluggable transport]: Combine traffic obfuscation with address diversity of flash proxy
#7167: Combine traffic obfuscation with address diversity of flash proxy
-----------------------------------------+----------------------------------
Reporter: karsten | Owner: asn
Type: project | Status: needs_revision
Priority: normal | Milestone:
Component: Pluggable transport | Version:
Keywords: SponsorF20131101 flashproxy | Parent:
Points: | Actualpoints:
-----------------------------------------+----------------------------------
Comment(by asn):
Howdy,
looking at the logic of `obfs-flash.git`, it seems that if we want a
bundle that contains `websocket`, `obfs2|websocket` and `obfs3|websocket`,
then we will have to spawn 3 `flashproxy-client`s and each one of them
will do its own registration.
That's fine, but each of those `flashproxy-client`s should be aware of the
transport chain it supports, so that it can submit a proper client
registraton to the facilitator.
How should we do this? Should we add a CLI swich to `flashproxy-client`
that looks like this: `--transport=websocket|obfs3`? Should we also be
able to specify a default port for that transport so that we can ask
people to forward a specific TCP port (like we currently do with
`DEFAULT_REMOTE_PORT`)?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7167#comment:28>
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