Thus spake Roger Dingledine ([EMAIL PROTECTED]): > Actually, it would be smarter to add a controller interface to let > the controller inform Tor of new opinions it should have. For example, > "this server is not running". Then we could do all the smarts in the > controller, where they should be. > > The actual interface will be a bit delicate though, since we want Tor > to do some of the thinking and the controller to do other of the thinking. > > As a first step though, we could make the controller changes sticky, > meaning that Tor doesn't do any thinking for servers that the controller > has given it an opinion on.
KO. An interface to suck a signature-verified directory out of Tor via the control-port or some other means would also be nice. > Check out > https://tor-svn.freehaven.net/svn/torctl/trunk/python/ Ok, I will consider rewriting it for this python interface. Have to learn python first, which has been on my TODO list for some time, so hopefully it will happen. I would guess the directory notification interface won't appear for a while in Tor either, so I probably have time. When 0.1.2 stabilizes? In the meantime I will keep my rickety perl running and will keep in contact with the list when I notice things. > Also check out Geoff's python Tor controller (which uses the above > scripts) at http://afs.eecs.harvard.edu/~goodell/blossom/ I actually had a look at blossom, but didn't see that it was using a standard torctl interface. Probably just me not groking python tho. -- Mike Perry Mad Computer Scientist fscked.org evil labs
