Expanded ORPort confuses arm
Proposal 186 greatly expands the ORPort option, so it's no longer simply just a single port number (it might have addresses, multiple ports, special attributes, etc).
This change breaks arm's GETCONF calls to figure out the ORPort. We should figure out how arm wants to handle and display information about these new capabilities.
On tor's side, implementation for this was added in... 5f0a8dcd2cfcbafc3deb3a6717808b607a459dac
According to the man page this stuff doesn't yet seem to be documented which is pesky... https://www.torproject.org/docs/tor-manual-dev.html
Issue caught by swalker.