Control port method to get the exit policy
Presently controllers can GETCONF the ExitPolicy, but not get the actual exit policy we're running with. It would be nice if it was exposed via the control port.
Here's what I ended up writing in stem to get around this...
19:23 < armadev> atagar: re f0ae1eaee, where were you seeing exit policies with redundant lines? tor tries to get rid of redundant lines too. i wonder if it doesn't do it well enough, or doesn't do it pervasively enough? 19:24 < armadev> atagar: ...perhaps tor doesn't export its exit policy to the control port at all 19:43 < atagar> armadev: I don't think that it does, so I wrote a method for getting it... 19:43 < atagar> https://gitweb.torproject.org/stem.git/commitdiff/716f8a693e9b814da5e2c9df551dbe6768f4f324 19:43 < atagar> It would be nicer to fetch via the control port though. :) 19:43 < armadev> for these cases, it would be great if you opened a tor ticket to say what you want exported 19:44 < atagar> ok, will do 19:44 < armadev> i guess there should be a balance between how much work tor does, and how much work the controller does 19:44 < armadev> but in general, if the argument can go "each controller would have to implement this thing itself, which is best done in tor", then it should go into tor
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information