[tor-bugs] #9166 [Tor]: Write a UTP-based channel implementation

[Tor Bug Tracker & Wiki]

#9166: Write a UTP-based channel implementation
------------------------+------------------------------
     Reporter:  nickm   |      Owner:
         Type:  defect  |     Status:  new
     Priority:  normal  |  Milestone:  Tor: unspecified
    Component:  Tor     |    Version:
   Resolution:          |   Keywords:  tor-relay utp
Actual Points:          |  Parent ID:  #9165
       Points:          |
------------------------+------------------------------

Comment (by karsten):

 Replying to [comment:28 sjmurdoch]:
 > Replying to [comment:27 robgjansen]:
 > > I get this error:
 > >
 > > {{{
 > > src/or/libtor.a(channeltls.o): In function `tor_UTPOnReadProc':
 > > channeltls.c:(.text+0x53e): undefined reference to `UTP_SetUserdata'
 > > }}}
 > >
 > > What am I missing?
 >
 > You will need to use my fork of libutp:
 https://github.com/sjmurdoch/libutp (master branch, currently
 569c044e8bd7b2a01476d4885c205f77be363d1f).

 Speaking of, we might get rid of our custom libutp branch if we do the
 following two things:

 - Call the existing UTP_SetCallbacks instead of the newly added
 UTP_SetUserdata, passing the same UTPFunctionTable as we pass to the other
 call of UTP_SetCallbacks.  This one is easy, I think.

 - Fix the
 [https://github.com/sjmurdoch/libutp/commit/52dd48278355be4a646e6fa3d3bc7ace866bb7ff
 other problem] that Steven found ("Needed -fPIC for compiling with Tor")
 without forking libutp.  I don't know enough about this compiler flag to
 suggest a fix.

 If somebody can suggest a fix to the second problem, I'll update the utp
 tor branch to use the official libutp branch.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9166#comment:31>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online