pluggable transports issueshttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/trac/-/issues2023-10-03T19:34:10Zhttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/trac/-/issues/40001Add support for dnstt2023-10-03T19:34:10ZanadahzAdd support for dnsttThis is the main issue for all the things that need to happen in order to add support for [dnstt](https://www.bamsoftware.com/software/dnstt/) PT.
Please feel free to edit/move this issue if needed.
According to the discussion we had i...This is the main issue for all the things that need to happen in order to add support for [dnstt](https://www.bamsoftware.com/software/dnstt/) PT.
Please feel free to edit/move this issue if needed.
According to the discussion we had in this week's [meeting](http://meetbot.debian.net/tor-meeting/2022/tor-meeting.2022-03-17-15.59.html), the following should happen:
- [x] Setup a test dnstt bridge (Implemented: http://eweiibe6tdjsdprb4px6rqrzzcsi22m4koia44kc5pcjr7nec2rlxyad.onion/tpo/anti-censorship/pluggable-transports/trac/-/issues/40001#note_2788292)
- [ ] add support for the [PT spec](https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt) in the dnstt client and server
- [ ] Add support for dnstt in BridgeDB and rdsys
- [ ] iOS and Android clients - [WIP](https://github.com/tladesignz/IPtProxy/commit/e2ce9d113c412f9baa436f641a61d6af465a3043)
- [ ] Get instruction on how to setup a dnstt bridge for different OSes - tpo/web/community#263
- [ ] Add support for dnstt in Tor Browser
- [ ] Write Tor Browser user documentation - tpo/web/manual#118
- [ ] Add default dnstt bridges as failover to Meek and Snowflakehttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/trac/-/issues/12930Someone, somewhere needs to unescape pluggable transport "SMETHOD ARGS" argum...2021-11-08T20:01:18ZYawning AngelSomeone, somewhere needs to unescape pluggable transport "SMETHOD ARGS" arguments.Per pt-spec.txt:
```
- ARGS:K=V,K=V,K=V
If this option is set, the K=V arguments are added to Tor's
extrainfo document. Equal signs and commas must be escaped
with a backslash.
```
All of obfs4's server (e...Per pt-spec.txt:
```
- ARGS:K=V,K=V,K=V
If this option is set, the K=V arguments are added to Tor's
extrainfo document. Equal signs and commas must be escaped
with a backslash.
```
All of obfs4's server (extra info) document arguments end with a number of equal signs because they are Base64 strings.
goptlib does the right thing here and escapes the args, so the trailing Base64 padding passed to tor as part of SMETHOD ARGS ends with `\\=`. The fun here is that, tor does not unescape the ARGS line, so `\\=` is what ends up in the extrainfo document on BridgeDB.
The arguments that appear on obfs4 bridge lines should not be escaped, so someone, somewhere between little-t tor, and the place where the arguments appear on whatever BridgeDB frontend the end user sees, needs to unescape the arguments.https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/trac/-/issues/11501Improve visual identity of Tor's PTs2021-11-08T19:53:05ZGeorge KadianakisImprove visual identity of Tor's PTsWe've been failing with naming Tor's censorship circumvention tech for a while ('Pluggable Transports', 'obfsproxy', 'obfs3', 'obfs2', 'flashproxy'...).
We know that our users are getting better at learning these terms, but we should tr...We've been failing with naming Tor's censorship circumvention tech for a while ('Pluggable Transports', 'obfsproxy', 'obfs3', 'obfs2', 'flashproxy'...).
We know that our users are getting better at learning these terms, but we should try to help them. I think establishing a visual identity for PTs through a logo, might help.
This way, we can put the same logo in the PT/obfsproxy homepage, and in BridgeDB, and in TBB (in the step of the wizard where you have to add your bridges), and people will learn that when they see that logo it's PT-related.
I'd currently use the obfsproxy logo:
![https://trac.torproject.org/projects/tor/attachment/ticket/5111/logo%20shaded.svg](https://trac.torproject.org/projects/tor/attachment/ticket/5111/logo%20shaded.svg)
except if someone tells me it's a terrible idea (I admit it's more silly than confidence inspiring, but I think it gets the point across). Any other suggestions are welcome.
If people think that this is a reasonable idea, I will create tickets for the BridgeDB and TBB mods.https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/trac/-/issues/10970tor-bridge-relay Debian package2021-11-08T19:58:52ZXimin Luotor-bridge-relay Debian packageInspired by https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/BridgeBundles
tor-bridge-relay will be a small native package that recommends all bridge servers and contains a torrc that uses them.
We ...Inspired by https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/BridgeBundles
tor-bridge-relay will be a small native package that recommends all bridge servers and contains a torrc that uses them.
We can also add bridge-specific documentation, e.g. advice like "if you are in country X then don't use transport Y because this opens your IP address up to a confirmation attack".
This should be fairly simple to implement, but I filed this bug to collect any comments that anyone might have.Ximin LuoXimin Luohttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/trac/-/issues/10677Run unit tests for pluggable transports when building Tor Browser Bundle2021-11-08T19:58:01ZkpdyerRun unit tests for pluggable transports when building Tor Browser Bundledcf and I were recently discussing the dependencies between pluggable transports in the Tor Browser Bundle. As an example obfsproxy, flashproxy, and fteproxy all rely on pyptlib.
In these cases it is important that we have sanity checks...dcf and I were recently discussing the dependencies between pluggable transports in the Tor Browser Bundle. As an example obfsproxy, flashproxy, and fteproxy all rely on pyptlib.
In these cases it is important that we have sanity checks to ensure that when one of these components is upgraded, it doesn't break any of the pluggable transports. It's tedious to manually verify that each pluggable transport works.
It appears that nearly all of the pluggable transports have unit tests. A simple sanity check, running all unit tests for all PTs during the build, is probably a good idea.kpdyerkpdyer