[tor-bugs] #7059 [Tor]: TorControl: Unrecognized (node) key errors

[Tor Bug Tracker & Wiki]

#7059: TorControl: Unrecognized (node) key errors
-----------------------------------+----------------------------------------
 Reporter:  mr-4                   |          Owner:  aagbsn            
     Type:  defect                 |         Status:  new               
 Priority:  normal                 |      Milestone:  Tor: 0.2.4.x-final
Component:  Tor                    |        Version:  Tor: 0.2.4.3-alpha
 Keywords:  tor-client controller  |         Parent:                    
   Points:                         |   Actualpoints:                    
-----------------------------------+----------------------------------------

Comment(by mr-4):

 Replying to [comment:20 nickm]:
 > As specified, no.  "ns/*" is for stuff in the consensus; "desc/" is for
 stuff for which you have router descriptors; "md" is for microdescriptors
 in particular.
 I can understand the "md" and "desc" part of the argument - it makes
 sense, but not the "ns" bit - the spec in particular doesn't make any
 distinction on whether microdescriptor information should only be
 included.

 If anything, it refers to the v2 format, which includes "router"
 descriptor info (which in itself includes IP address, OR port etc), so I
 think this should be properly enforced. From the control-spec.txt
 document:

 "...the latest router status info (v2 directory style) for a given OR.
 Router status info is as given in dir-spec.txt, and reflects the current
 beliefs of this Tor about the router in question."

 > It might be neat to have a "node" item that merged all the info we knew
 about a router and returned it in a reasonable format, but that feels like
 another ticket.
 To me, that's the function of "ns", but if that is not the case I can
 submit another ticket for this - no problem.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7059#comment:21>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online