Re: [tor-bugs] #29285 [Circumvention/Pluggable transport]: Improve the PT spec and how PTs interface with Tor

[Tor Bug Tracker & Wiki]

#29285: Improve the PT spec and how PTs interface with Tor
---+---
 Reporter:  cohosh |  Owner:  phw
 Type:  project| Status:  assigned
 Priority:  High   |  Milestone:
Component:  Circumvention/Pluggable transport  |Version:
 Severity:  Normal | Resolution:
 Keywords:  anti-censorship-roadmap-2020Q1 |  Actual Points:
Parent ID: | Points:  15
 Reviewer: |Sponsor:
   |  Sponsor28-must
---+---
Changes (by gaba):

 * keywords:  anti-censorship-roadmap-october => anti-censorship-roadmap-
 2020Q1


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29285 [Circumvention/Pluggable transport]: Improve the PT spec and how PTs interface with Tor

[Tor Bug Tracker & Wiki]

#29285: Improve the PT spec and how PTs interface with Tor
---+---
 Reporter:  cohosh |  Owner:  phw
 Type:  project| Status:  assigned
 Priority:  High   |  Milestone:
Component:  Circumvention/Pluggable transport  |Version:
 Severity:  Normal | Resolution:
 Keywords:  anti-censorship-roadmap-october|  Actual Points:
Parent ID: | Points:  15
 Reviewer: |Sponsor:
   |  Sponsor28-must
---+---
Changes (by gaba):

 * keywords:  anti-censorship-roadmap-august => anti-censorship-roadmap-
 october


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29285 [Circumvention/Pluggable transport]: Improve the PT spec and how PTs interface with Tor

[Tor Bug Tracker & Wiki]

#29285: Improve the PT spec and how PTs interface with Tor
---+---
 Reporter:  cohosh |  Owner:  phw
 Type:  project| Status:  assigned
 Priority:  High   |  Milestone:
Component:  Circumvention/Pluggable transport  |Version:
 Severity:  Normal | Resolution:
 Keywords:  anti-censorship-roadmap-august |  Actual Points:
Parent ID: | Points:  15
 Reviewer: |Sponsor:
   |  Sponsor28-must
---+---
Changes (by gaba):

 * keywords:  network-team-roadmap-2019-Q1Q2, anti-censorship-roadmap =>
 anti-censorship-roadmap-august


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29285 [Circumvention/Pluggable transport]: Improve the PT spec and how PTs interface with Tor

[Tor Bug Tracker & Wiki]

#29285: Improve the PT spec and how PTs interface with Tor
-+-
 Reporter:  cohosh   |  Owner:  phw
 Type:  project  | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Circumvention/Pluggable transport|Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-2019-Q1Q2,  |  Actual Points:
  anti-censorship-roadmap|
Parent ID:   | Points:  15
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-
Changes (by msherr):

 * cc: msherr (added)


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29285 [Circumvention/Pluggable transport]: Improve the PT spec and how PTs interface with Tor

[Tor Bug Tracker & Wiki]

#29285: Improve the PT spec and how PTs interface with Tor
-+-
 Reporter:  cohosh   |  Owner:  phw
 Type:  project  | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Circumvention/Pluggable transport|Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-2019-Q1Q2,  |  Actual Points:
  anti-censorship-roadmap|
Parent ID:   | Points:  15
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-

Comment (by teor):

 We also want to be able to assign multiple addresses to each pluggable
 transport. For example, and IPv4 and IPv6 address.
 See #30953 for details.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29285 [Circumvention/Pluggable transport]: Improve the PT spec and how PTs interface with Tor

[Tor Bug Tracker & Wiki]

#29285: Improve the PT spec and how PTs interface with Tor
-+-
 Reporter:  cohosh   |  Owner:  phw
 Type:  project  | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Circumvention/Pluggable transport|Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-2019-Q1Q2,  |  Actual Points:
  anti-censorship-roadmap|
Parent ID:   | Points:  15
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-

Comment (by phw):

 #21816 (Add support for Pluggable Transports 2.0) is related.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29285 [Circumvention/Pluggable transport]: Improve the PT spec and how PTs interface with Tor

[Tor Bug Tracker & Wiki]

#29285: Improve the PT spec and how PTs interface with Tor
-+-
 Reporter:  cohosh   |  Owner:  phw
 Type:  project  | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Circumvention/Pluggable transport|Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-2019-Q1Q2,  |  Actual Points:
  anti-censorship-roadmap|
Parent ID:   | Points:  15
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-

Comment (by dcf):

 Replying to [comment:8 mcs]:
 > The module within Tor Launcher that implements Moat (interactive bridge
 retrieval) is another example of the above. We did that so we could reuse
 your Meek PT implementation. See https://gitweb.torproject.org/tor-
 launcher.git/tree/src/modules/tl-bridgedb.jsm?h=maint-0.2.18#n188

 Oh good call, IIRC on the server side of Moat as well there is some half-
 baked shell script managing the meek-server process, that could be
 replaced with ptadapter (#29096).

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29285 [Circumvention/Pluggable transport]: Improve the PT spec and how PTs interface with Tor

[Tor Bug Tracker & Wiki]

#29285: Improve the PT spec and how PTs interface with Tor
-+-
 Reporter:  cohosh   |  Owner:  phw
 Type:  project  | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Circumvention/Pluggable transport|Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-2019-Q1Q2,  |  Actual Points:
  anti-censorship-roadmap|
Parent ID:   | Points:  15
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-
Changes (by mcs):

 * cc: brade, mcs (added)


Comment:

 Replying to [comment:7 dcf]:
 > Replying to [comment:5 phw]:
 > > And here's an incomplete list of existing library implementations:
 >
 > Really there are two types of PT implementations, or three if you count
 PT 2.0 additions. There aren't really standard names for these.
 > 1. IPC manager/dispatcher. As far as I know, tor and
 [https://github.com/twisteroidambassador/ptadapter] are the only two
 implementations of this. This is the thing that sets e.g.
 `TOR_PT_MANAGED_TRANSPORT_VER` and manages subprocesses of type (2).

 The module within Tor Launcher that implements Moat (interactive bridge
 retrieval) is another example of the above. We did that so we could reuse
 your Meek PT implementation. See https://gitweb.torproject.org/tor-
 launcher.git/tree/src/modules/tl-bridgedb.jsm?h=maint-0.2.18#n188

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29285 [Circumvention/Pluggable transport]: Improve the PT spec and how PTs interface with Tor

[Tor Bug Tracker & Wiki]

#29285: Improve the PT spec and how PTs interface with Tor
-+-
 Reporter:  cohosh   |  Owner:  phw
 Type:  project  | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Circumvention/Pluggable transport|Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-2019-Q1Q2,  |  Actual Points:
  anti-censorship-roadmap|
Parent ID:   | Points:  15
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-

Comment (by dcf):

 Replying to [comment:5 phw]:
 > And here's an incomplete list of existing library implementations:

 Really there are two types of PT implementations, or three if you count PT
 2.0 additions. There aren't really standard names for these.
 1. IPC manager/dispatcher. As far as I know, tor and
 [https://github.com/twisteroidambassador/ptadapter] are the only two
 implementations of this. This is the thing that sets e.g.
 `TOR_PT_MANAGED_TRANSPORT_VER` and manages subprocesses of type (2).
 2. IPC transport/plugin. This is goptlib and pyptlib. It's a subprocess
 managed by an implementation of type (1). This is the thing that writes
 e.g. `CMETHOD` to stdout.
 3. From PT 2.0, there are also plugin/transport implementations that you
 are meant to link with directly in the same executable, without going
 through the IPC interface. There are [https://github.com/Pluggable-
 Transports/Pluggable-Transports-
 
spec/blob/master/releases/PTSpecV2.1Draft1/Pluggable%20Transport%20Specification%20v2.1%20-%20Go%20Transport%20API%20v2.1%2C%20Draft%201.pdf
 Go] and [https://github.com/Pluggable-Transports/Pluggable-Transports-
 
spec/blob/master/releases/PTSpecV2.1Draft1/Pluggable%20Transport%20Specification%20v2.1%20-%20Swift%20Transport%20API%20v1.0%2C%20Draft%201.pdf
 Swift] API spec. From talking to Brandon Wiley, my understanding is that
 everything that uses PT other than tor and ptadapter uses such an API, or
 something like it, not the IPC model.
 [https://github.com/OperatorFoundation/shapeshifter-dispatcher
 shapeshifter-dispatcher] converts implementations of type (3) into type
 (2).

 The [https://github.com/Pluggable-Transports/Pluggable-Transports-
 
spec/blob/master/releases/PTSpecV2.1Draft1/Pluggable%20Transport%20Specification%20v2.1%20-%20Base%20Specification%20v2.1%2C%20Draft%201.pdf
 Pluggable Transports Base Spec v2.1] calls types (1) and (2) "IPC" and
 type (3) "API".

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29285 [Circumvention/Pluggable transport]: Improve the PT spec and how PTs interface with Tor

[Tor Bug Tracker & Wiki]

#29285: Improve the PT spec and how PTs interface with Tor
-+-
 Reporter:  cohosh   |  Owner:  phw
 Type:  project  | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Circumvention/Pluggable transport|Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-2019-Q1Q2,  |  Actual Points:
  anti-censorship-roadmap|
Parent ID:   | Points:  15
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-

Comment (by phw):

 We now have a discussion thread on [https://lists.torproject.org/pipermail
 /tor-dev/2019-June/013879.html tor-dev@] and I started pointing some
 implementers to this thread in the hope that they will share their
 experience.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #29285 [Circumvention/Pluggable transport]: Improve the PT spec and how PTs interface with Tor

[Tor Bug Tracker & Wiki]

#29285: Improve the PT spec and how PTs interface with Tor
-+-
 Reporter:  cohosh   |  Owner:  phw
 Type:  project  | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Circumvention/Pluggable transport|Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-2019-Q1Q2,  |  Actual Points:
  anti-censorship-roadmap|
Parent ID:   | Points:  15
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-
Changes (by phw):

 * status:  new => assigned
 * cc: arma, gaba (added)
 * priority:  Medium => High
 * keywords:  network-team-roadmap-2019-Q1Q2 => network-team-
 roadmap-2019-Q1Q2, anti-censorship-roadmap
 * points:   => 15
 * sponsor:  Sponsor19 => Sponsor28-must
 * owner:  (none) => phw


Comment:

 Here's an incomplete list of issues with our current spec:
 * The PT should be able to communicate its bootstrap status to the
 invoking process.
 * The spec should incorporate the proposed dormant mode (see #28849).
 * Some PTs such as meek and snowflake don't rely on an IP address. The
 current workaround is to use awkward pseudo IP addresses.
 * Other transports may want to rely on multiple IP address. We need to
 reconsider the outdated notion of a bridge line. The PT should be able to
 communicate its bootstrap status to the invoking process.
 * The spec should incorporate the proposed dormant mode (see #28849).
 * Some PTs such as meek and snowflake don't rely on an IP address. The
 current workaround is to use awkward pseudo IP addresses.
 * Other transports may want to rely on multiple IP address. We need to
 reconsider the outdated notion of a bridge line.

 And here's an incomplete list of existing library implementations:
 * [https://github.com/operatorfoundation/transport A seemingly unnamed
 Swift implementation] of the v2.1 specification, maintained by the
 Operator Foundation.
 * [https://github.com/guardianproject/AndroidPluggableTransports PLUTO2]
 is a Java implementation of the v2.x specification, maintained by the
 Guardian Project.
 * [https://gitweb.torproject.org/pluggable-transports/goptlib.git/
 goptlib] is a Go implementation of the v1.0 specification, maintained by
 the Tor Project.
 * [https://gitweb.torproject.org/pluggable-transports/pyptlib.git/
 pyptlib] is a Python implementation of the v1.0 specification, (formerly)
 maintained by the Tor Project.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs