Hi Damian !
Thanks for your answer.
On 07/23/2013 06:00 PM, Damian Johnson wrote:
- The tor project generally dislikes other projects using the name
'tor' within them. This is why I called my projects arm and stem (arm was actually originally called tormoni, a name I still like a lot better)...
I was not aware of that. But when I read "That said, if the research paper comes with software, and that software could potentially confuse people (users or other researchers) about whether it's written or endorsed by The Tor Project, then we're back to the above scenariohttps://www.torproject.org/docs/trademark-faq.html.en#combining."
I think there is no way my "software" (which is not event a software, more a framework or DSL to speak the TOR protocol). Think of it as a research paper. Written in Python ;-).
More seriously, it's not a software intended to be run by Tor users or even Tor relay operators, it's a framework intended to be used by Tor developers / hackers to play with implementations of the Tor protocol.
- Stem might be able to help you a great deal with this project. It's
not just a client of tor's control port, but also a python implementation of its directory specification. For starters I'd look at its new remote descriptor fetching module to pull descriptor content...
https://stem.torproject.org/ https://stem.torproject.org/api/descriptor/remote.html
I just had a look at this project, and if I understand well, it speaks to a Tor's control port and gets its data from the Tor client. With TorPylle, I want to be able to fetch data from any Directory Server directly, and act more or less "as if" I was a Tor client.
To be sure people understand what I mean, the examples.py file in the repository shows what you can do with TorPylle (for now, keep in mind it's a work in progress).
But there are ideas in stem I could use in TorPylle !
Thanks again,
Pierre