[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #18856 [Core Tor/Stem]: Talk with tor's ORPort
#18856: Talk with tor's ORPort
---------------------------+------------------------
Reporter: atagar | Owner: atagar
Type: enhancement | Status: new
Priority: Low | Milestone:
Component: Core Tor/Stem | Version:
Severity: Minor | Resolution:
Keywords: descriptor | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
---------------------------+------------------------
Comment (by teor):
Replying to [comment:5 atagar]:
> Sorry, I might be missing something. Quick look seems to indicate
Trunnel is some C parser thing?
>
> http://www.wangafu.net/~nickm/trunnel-manual.html
>
> How is this related to this?
Trunnel takes a binary format definition, and produces C code that
generates and parses that definition.
Tor comes with a set of trunnel definitions for some of its binary
formats, and is migrating to trunnel for the rest.
> And are you advocating for stem to distribute native code? If so that
would be a big wrinkle for distribution.
No, we could teach trunnel to produce python code that generates and
parses binary format definitions, then use the tor trunnel definitions to
generate them.
> Is the argument that the ORPort protocol is so tricky only native code
can talk with it? If so then this ticket indeed might be moot.
No, I'm sure you can do it in python. It's just bit and byte manipulation.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18856#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs