Opened 6 years ago

Closed 4 years ago

Last modified 3 years ago

#9580 closed enhancement (wontfix)

Tor should accept combined pluggable transport names

Reported by: asn Owned by:
Priority: Very Low Milestone:
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-pt 025-backport needs-spec easy 026-triaged-1 026-deferrable easy
Cc: dcf Actual Points:
Parent ID: #10061 Points: small
Reviewer: Sponsor:

Description

The plan for #7167 is to have flashproxy understand pluggable transporst like "websocket|obfs2", that is the combination of websocket and obfs2.

The good thing about our plan for #7167 is that it requires no real modifications to little-t-tor. However, in little-t-tor we do some checks on the transport names (in torrc, etc.) and ensure that they are C-identifiers -- but "websocket|obfs2" is not a C-identifier.

We should relax those checks so that they don't choke when we give them "websocket|obfs2".

Child Tickets

Change History (11)

comment:1 Changed 6 years ago by dcf

As a workaround in #7167, we are using the transport name "obfs3_flash", and mapping it internally to obfs3|websocket.

comment:2 Changed 6 years ago by infinity0

Parent ID: #7167#10061

Re-parenting to the ticket for the general composer.

comment:3 Changed 6 years ago by nickm

Keywords: tor-pt 025-backport needs-spec added
Milestone: Tor: 0.2.6.x-final

This is pretty easy if you still want it. It just needs a change to the parsing code and to the spec.

comment:4 Changed 5 years ago by nickm

Keywords: easy 026-triaged-1 026-deferrable added
Priority: normalminor
Type: defectenhancement

comment:5 Changed 5 years ago by nickm

Keywords: tor-pt 025-backport needs-spec easy 026-triaged-1 026-deferrabletor-pt 025-backport needs-spec easy 026-triaged-1 026-deferrable easy

comment:6 Changed 5 years ago by asn

Milestone: Tor: 0.2.6.x-finalTor: 0.2.???

Moving this to tor-0.2.?? till we decide what we want to do with fog.

comment:7 Changed 4 years ago by nickm

Points: small
Priority: LowVery Low
Severity: Normal
Status: newneeds_information

Do we still actually want this?

comment:8 Changed 4 years ago by infinity0

I haven't worked on this for a long time and there's no current use-case for it.

It might become useful in the future if:

  • a padding-based PT gets made (or is tor going to include that within itself?) and then we could use it with flashproxy/snowflake again, or
  • we are somehow able to run different protocols via browser-proxies apart from websocket/webrtc

But for now, feel free to close this ticket.

comment:9 Changed 4 years ago by nickm

Resolution: wontfix
Status: needs_informationclosed

Closing as wontfix; please reopen if anybody wants it.

comment:10 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:11 Changed 3 years ago by nickm

Milestone: Tor: 0.3.???

Milestone deleted

Note: See TracTickets for help on using tickets.