[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-bugs] #3435 [Tor Relay]: Bad State Parsing

#3435: Bad State Parsing
-----------------------+----------------------------------------------------
 Reporter:  atagar     |          Owner:     
     Type:  defect     |         Status:  new
 Priority:  minor      |      Milestone:     
Component:  Tor Relay  |        Version:     
 Keywords:             |         Parent:     
   Points:             |   Actualpoints:     
-----------------------+----------------------------------------------------
 On occasion when I'm doing excessive restarts of Tor (especially when
 triggering it to crash) my state gets to be something that causes Tor
 repeatedly to error:

 Jun 19 13:30:56.799 [warn] router_rebuild_descriptor(): Bug: Couldn't
 generate router descriptor.
 Jun 19 13:30:58.395 [warn] Invalid bandwidthcapacity "10485760"
 Jun 19 13:30:58.395 [err] router_dump_router_to_string(): Bug: We just
 generated a router descriptor we can't parse.
 Jun 19 13:30:58.395 [err] router_dump_router_to_string(): Bug: Descriptor
 was: <<router armTest 67.137.76.214 9001 0 0
 platform Tor 0.2.2.19-alpha (git-7ca7b6ebdcfb8c42) on Linux i686
 opt protocols Link 1 2 Circuit 1
 published 2011-06-19 20:30:58
 opt fingerprint 30BE FE1F 8E07 FAD8 30EA 885C 2E06 7F17 4AB4 8BD3
 uptime 12
 bandwidth 5242880 10485760 -2147483648
 opt extra-info-digest B6DF89ED7F30409C339F23FB37C84CC1A62D530C
 onion-key
 -----BEGIN RSA PUBLIC KEY-----
 MIGJAoGBAL1v5fRLR1zHq8xUcVQ0oqFQq0CRfieogBk4Mkc0YjD060PKUR37vbpt
 N2zC3cbru7jMa6nVJPiPWhK26IfA2FGTVvrk6tC0j3zZs1OizFzXEpznPkOIJo20
 rBa4bU0RPrLDxKGKsCAHbghDJ7a18DUl8jfP9s6+wB3mPDR0DxyfAgMBAAE=
 -----END RSA PUBLIC KEY-----
 signing-key
 -----BEGIN RSA PUBLIC KEY-----
 MIGJAoGBALrq7P9TzV9jaTnM4FktaAmsBg4nD/Knwr0B/zcJaQTf3rPslMlIR+Z6
 nKds79/FwB+Agyw0OeHLOdgMd0rwsi8iF7lC0hEwLv8bdkkk5JdQz3qN5jAYKWZZ
 XwuxOfeMGPinaO58vEftGKnhK1hbLJfGDirDE89bX6tsVM72sPkPAgMBAAE=
 -----END RSA PUBLIC KEY-----
 opt hidden-service-dir
 reject *:*
 router-signature
 -----BEGIN SIGNATURE-----
 Rgy8H5lb0+zAeAk69RFwHVDLAmZqJvgSi8G/8KxddZhHhSvFUzy0QxzHLargZGui
 JQZ+3ZJH7io5WaonU2LMwNMPPBsM2VtWsdbXv7TBmY60VUrqG+xBpUWM8KYFiqpw
 LqID34Da0rN1jS85p+bcEyJVFcG3GcGhUTMXtKBzOwI=
 -----END SIGNATURE-----

 Deleting the state file fixes the issue and, for me at least, using the
 attached state with a new Tor instance causes it to choke this way.

 This issue is infrequent and easy to address, but I'm not sure if this is
 revealing a tor issue we want to address in tor. Feel free to close if
 not.

 The bad state was generated with an old Tor version, but logs the same
 entries with Tor v0.2.2.19-alpha (git-7ca7b6ebdcfb8c42)

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