Re: [tor-bugs] #9286 [Tor]: ordb1 uses milliseconds in its descriptor, spec says it can't

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#9286: ordb1 uses milliseconds in its descriptor, spec says it can't
--------------------+-------------------------------------------------------
 Reporter:  arma    |          Owner:                    
     Type:  defect  |         Status:  new               
 Priority:  normal  |      Milestone:  Tor: 0.2.5.x-final
Component:  Tor     |        Version:                    
 Keywords:          |         Parent:                    
   Points:          |   Actualpoints:                    
--------------------+-------------------------------------------------------

Comment(by atagar):

 >>> and who knows what other parsing tools, now and in the future, will
 get upset by it.

 For stems part the descriptor parser validation will fail with...

 {{{
 >>> datetime.datetime.strptime("published 2013-07-17 13:38:46.992",
 "%Y-%m-%d %H:%M:%S")
 ValueError: time data 'published 2013-07-17 13:38:46.992' does not match
 format '%Y-%m-%d %H:%M:%S'
 }}}

 If you disable descriptor validation then the published attribute will
 simply be unset.

 Possibly a crazy thought but maybe some directory authorities should run
 stem's descriptor parser over the consensuses they publish? Stem's
 validation checks for pretty strict conformance to the spec, so it's
 likely catch issues tor itself doesn't (see the results from #7828). I've
 also thought about writing a script to pull each consensus on my side and
 validate it - easy to do once I've finished with this remote descriptor
 fetching API.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9286#comment:6>
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