[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #4257 [Torctl]: Stem / TorCtl Integration
#4257: Stem / TorCtl Integration
-------------------------+--------------------------------------------------
Reporter: atagar | Owner: mikeperry
Type: enhancement | Status: needs_review
Priority: normal | Milestone:
Component: Torctl | Version:
Keywords: | Parent:
Points: | Actualpoints:
-------------------------+--------------------------------------------------
Comment(by aagbsn):
Replying to [comment:7 atagar]:
> > Unless I can convince you it would be fun to run an exit scanner using
stem underneath?
>
> I have my hands full enough getting this library written, and the bar a
change needs to pass before being deemed sufficient safe seems like a call
that you should be making. I manually test TorCtl changes before sending
them on to you (of course - details in commit description) so from my
point of view they're good to go.
From my perspective, the first test I run against TorCtl is BwAuthority.
If that test fails, I am willing to investigate, but I have my hands full
enough too :-). See for instance #4015. This issue is a show-stopper for
BwAuthority; an issue I have put several days of time into.
If we want to proceed with Stem & TorCtl integration, core applications
have to work. It would be a huge help to mike and I if you could test your
TorCtl changes against live BwAuthority and ExitAuthority instances. If
you aren't sure where to start, I can help you set these up and answer any
questions. And if you don't have infrastructure, I can give you access to
infrastructure.
--Aaron
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4257#comment:8>
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