Feature #8287
Explain what is required to have new pluggable transports
100%
Description
So far we are maintaining a list of available pluggable transports in /doc/first_steps/startup_options/bridge_mode but people often ask for more transports. But it would also be helpful to explain why newer transports are not supported and what needs to be done.
Let’s agree first on a rationale for that and then we can decide where to put it. If the explanation is small enough it could fit directly on /doc/first_steps/startup_options/bridge_mode otherwise we might want to write a more complete FAQ.
So what is required for the inclusion of a new pluggable transports?
Subtasks
| Feature #8521: Explain detailed technical requirements for new pluggable transports | Rejected | 0 |
|||
| Feature #8522: Summarize why we don't include all possible pluggable transports | Rejected | 0 |
History
#1 Updated by sajolida 2014-11-22 11:54:26
Having it in Debian
#2 Updated by sajolida 2015-01-03 19:04:12
See https://mailman.boum.org/pipermail/tails-dev/2014-November/007382.html and subthreads.
The output should probably be double:
- design documentation:
Feature #8521 - end user documentation:
Feature #8522
#3 Updated by Anonymous 2017-06-30 14:25:21
- related to
Feature #8243: Support meek bridges added
#4 Updated by Anonymous 2018-01-17 16:46:41
- Status changed from Confirmed to Rejected
It seems the need to more PT from TBB tarball is much lower than it used to and the discussion started on tails-dev never reached a conclusion. So this documentation might actually be obsolete nowadays, or too costly compared to the benefit it’ll bring. -> Rejecting.
#5 Updated by Anonymous 2018-01-17 16:49:55
- Status changed from Rejected to Confirmed
#6 Updated by Anonymous 2018-01-17 16:50:33
- Status changed from Confirmed to Rejected