Opened 8 years ago

Closed 7 years ago

#5256 closed enhancement (fixed)

Switch to stem from PyTorCtl

Reported by: hellais Owned by: hellais
Priority: Medium Milestone:
Component: Archived/Ooni Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

It appears to be the case that PyTorCtl is not longer actively developed and it has some issues with Tor 0.2.3.x.

It has been advised to remove all the TorCtl dependent code from BridgeT and port it over to stem.

Child Tickets

Change History (2)

comment:1 Changed 8 years ago by atagar

My plan for stem was to...

  1. Implement the Controller class, which will be very similar to the TorCtl Connection class. This will take a couple months to implement after I'm no longer distracted with GSoC, metrics-lib, and safe cookie. (hint: help would be appreciated)
  1. Migrate arm to stem to work out problems with the API.
  1. Work on a PathSupport counterpart then migrate TorBEL.
  1. Tidy up any other features that we need for parity, settle on an API, then make a release announcement.

Note that I won't have an API set in stone until I make a release announcement. However, if you'd like BridgeT to be an alpha client then I can help you with migrating after the Controller class is done, then submit patches to you if I make any breaking changes.

Cheers! -Damian

comment:2 Changed 7 years ago by hellais

Resolution: fixed
Status: newclosed

We have decided to move over to txtorcon instead of stem since our codebase is heavily based on Twisted and txtorcon plays well with it.

Note: See TracTickets for help on using tickets.